| 24 May 2026 |
 tks_123 | Yes, everyday local dev :) But... for everyday local dev, I'd want to... check if the website ... works in the browser (I guess)? | 13:08:19 |
| tks_123 | * Yes, everyday local dev :) But... for everyday local dev, I'd want to... check if the website ... works in the browser. | 13:08:50 |
| tks_123 | while also develop the website's frontend and backend (in vscode) | 13:09:20 |
| tks_123 | (yes how the final thing is built is technically a separate question..) | 13:09:42 |
| tks_123 | * while also developing the website's frontend and backend (in vscode) | 13:10:02 |
 alexfmpe | Oh gotcha. Out of habit I was assuming jsaddle-warp for dev so the frontend would also be using native builds | 13:26:23 |
| alexfmpe | But it sounds like you don't assume that for your project | 13:27:43 |
| tks_123 | alexfmpe Hmm, it seems I was using jsaddle 2-3 years ago in my projects. it seems for some reason i wasn't aware of jsaddle-warp :S | 13:48:03 |
| tks_123 | so i thought i had to always run a full ghcjs (the old ghcjs in this case) build just to preview my web apps... :S | 13:48:30 |
| tks_123 | which makes me wonder, why i was even using jsaddle. Now i'm confused | 13:49:11 |
| tks_123 | * which makes me wonder, why i was even using jsaddle | 13:49:29 |
| tks_123 | This is how my JS program looked:
main :: IO ()
main = do
doc <- jsg "document"
x <- doc ^. js1 "getElementById" "jspage"
-- ...
Some of the imported modules:
import GHCJS.Foreign.Callback
import GHCJS.Marshal
import GHCJS.Types
import JSDOM.Custom.Window
Some of the packages in the .cabal file:
ghcjs-base
ghcjs-dom
jsaddle
jsaddle-dom
| 13:53:56 |
| tks_123 | Are these things (modules, cabal packages) still relevant for the new JS backend? (Is this still the modern way to do it?) | 13:54:32 |
| tks_123 | * This is how my JS program looked:
main :: IO ()
main = do
doc <- jsg "document"
x <- doc ^. js1 "getElementById" "foo"
-- ...
Some of the imported modules:
import GHCJS.Foreign.Callback
import GHCJS.Marshal
import GHCJS.Types
import JSDOM.Custom.Window
Some of the packages in the .cabal file:
ghcjs-base
ghcjs-dom
jsaddle
jsaddle-dom
| 13:55:00 |
| alexfmpe | jsaddle-* all works with js backend just the same | 13:57:37 |
| alexfmpe | same for ghcjs-dom | 13:57:53 |
| alexfmpe | dunno ghcjs-base | 13:57:56 |
| tks_123 | Ok, great. Thanks! | 14:56:33 |
| tks_123 | Seems truly nothing changed, other than the GHCJS->backend switch in the background | 14:56:53 |
| tks_123 | (so major change, but in the background) | 14:57:02 |
| 25 May 2026 |
|  @jmchapman:matrix.org joined the room. | 10:32:11 |
| @jmchapman:matrix.org left the room. | 10:32:24 |
 Ember | hey I still do this because the warp version doesn't load properly | 22:15:59 |
| Ember | well, last time I tried it anyway, because firefox did something standards compliant whereas chrome didn't, afaicr | 23:11:37 |
| Ember | will have to try this again soon | 23:11:45 |
| 26 May 2026 |
| alexfmpe | Ah yeah jsaddle-warp didn't work on firefox | 06:25:25 |
| alexfmpe | I think it's supposed to work nowadays? | 06:25:44 |
|  phanirithvij changed their display name from loudgolem to phanirithvij. | 11:40:40 |
 sterni | The question is of course what to do about master which is going to become 26.05. We've patched some packages so they work with the deprecated Hakyll version, but it's probably annoying to ship it. | 16:50:08 |
| sterni | Not sure which way to go is easier though, probably reverting the update | 16:50:17 |
