Since updating to the IR compiler i’ve noticed tha...
# javascript
g
Since updating to the IR compiler i’ve noticed that the
jsBrowserDevelopment
task now causes two browser reloads. When i save a file: 1. the re-compile step starts BUT at the same time it looks like the websocket for webpack gets a reload signal 2. so, the browser reloads for webpack dev server websocket signal 3. then it reloads AGAIN when the kotlin compiler finishes the
jsMainClasses
task Is anyone else seeing this and if so is there a fix?
r
I’ve been seeing it as long as I’ve been using the feature (which I only just started using again last week after a long period of dormancy) no ideas on a fix, but you are not alone
I tend to wait to see the compile task finish before tabbing to the browser
g
yep. that’s what i’m doing too. it’s confusing when working on a laptop tho. i think i’ll file a bug ticket for this
👍 3
If I had to guess it's an issue with the file watcher and webpack. Clearly webpack is listening to the file system and reloading the js pipeline and then the kotlin compiler is re-triggering that. Maybe I'll look into the webpack listener portion of things
l
Would be great to report that on kotl.in/issue and link it in this thread.