 | Scala JS | 2133 Members |
| Scala.js, the Scala to JavaScript compiler | 9 Servers |
| Scala JS | 2133 Members |
| Scala.js, the Scala to JavaScript compiler | 9 Servers |
| Sender | Message | Time |
|---|---|---|
| 31 May 2024 | ||
 sjrd | If you have specific questions about Scala.js, we can help. But we won't do your homework for you. 😉 | 05:54:23 |
 .pierrelm joined the room. | 09:25:42 | |
 raulwastaken_ changed their display name from RaulWasTaken to raulwastaken_. | 12:32:14 | |
 alex037635 joined the room. | 20:30:22 | |
 nikitaga | Hey folks, question for Windows users: For typical Scala.js development, you run an sbt session with ~compile or ~fastLinkJS, and then also you start the Vite dev server, and if that uses the Scala.js vite plugin, that plugin also runs the sbt command when it starts. If you do this – does this work for you naturally? One person is reporting that they needed to specify SBT_SERVER_FORCESTART=1 env for that to work, otherwise they get a "could not create lock" error from sbt. And there's even an issue about that: https://github.com/sbt/sbt/issues/6777I don't use Windows myself so I'm wondering if I need to include that in my instructions for Windows users. And while we're on the topic, another Windows question right away: is Process("npm run build", ...) the correct way to run the npm script on Windows from build.sbt? Or does it need to be npm.cmd or npm.bat or cmd /c npm? | 23:06:24 |
| nikitaga | * Hey folks, question for Windows users: For typical Scala.js development, you run an sbt session with ~compile or ~fastLinkJS, and then also you start the Vite dev server, and if that uses the Scala.js vite plugin, that plugin also runs the sbt command when it starts. If you do this – does this work for you naturally? One person is reporting that they needed to specify SBT_SERVER_FORCESTART=1 env for that to work, otherwise they get a "could not create lock" error from sbt. And there's even an issue about that: https://github.com/sbt/sbt/issues/6777I don't use Windows myself so I'm wondering if I need to include that in my instructions for Windows users (for the Laminar demo project). And while we're on the topic, another Windows question right away: is Process("npm run build", ...) the correct way to run the npm script on Windows from build.sbt? Or does it need to be npm.cmd or npm.bat or cmd /c npm? | 23:06:42 |
| nikitaga | * Hey folks, question for Windows users: For typical Scala.js development, you run an sbt session with ~compile or ~fastLinkJS, and then also you start the Vite dev server, and if that uses the Scala.js vite plugin, that plugin also runs the sbt command when it starts. If you do this – does this work for you naturally? One person is reporting that they needed to specify SBT_SERVER_FORCESTART=1 env for that to work, otherwise they get a "could not create lock" error from sbt. And there's even a relevant issue: https://github.com/sbt/sbt/issues/6777I don't use Windows myself so I'm wondering if I need to include that in my instructions for Windows users (for the Laminar demo project). And while we're on the topic, another Windows question right away: is Process("npm run build", ...) the correct way to run the npm script on Windows from build.sbt? Or does it need to be npm.cmd or npm.bat or cmd /c npm? | 23:07:27 |
 aly.fish | cmd /c npm is the safest way | 23:09:48 |
| aly.fish |  Download image.png | 23:10:07 |
| aly.fish | for me, npm wouldn't get picked up by Process | 23:10:07 |
| aly.fish | | 23:11:50 |
| aly.fish | | 23:12:18 |
| nikitaga | aly.fish Thanks, what about npm.cmd, does that ring a bell on Windows? From what I've read it seems to be a more direct Windows alternative to running npm command on other systems, in that cmd /c npm executes npm in a clean environment without inheriting env vars (or something like that) which is not typically the case. | 23:35:49 |
| nikitaga | * aly.fish Thanks! What about npm.cmd, does that ring a bell on Windows? From what I've read it seems to be a more direct Windows alternative to running npm command on other systems, in that cmd /c npm executes npm in a clean environment without inheriting env vars (or something like that) which is not typically the case. | 23:35:57 |
| aly.fish | cmd /c npm will look for all 3 of npm.cmd npm.ps1 npm.exe | 23:36:16 |
| nikitaga | * aly.fish Thanks! What about npm.cmd, does that ring a bell on Windows? From what I've read it seems to be a more direct Windows alternative to running npm command on other systems, in that cmd /c npm executes npm in a clean environment without inheriting env vars (or something like that) which is not typically the case when just running npm. | 23:36:20 |
| nikitaga | And a user may have one of them but not others, e.g. if they installed npm in a different way? | 23:36:59 |
| aly.fish | Yep | 23:37:04 |
| nikitaga | I see, thanks, I guess I'll need to do that. | 23:37:25 |
| 1 Jun 2024 | ||
 granarder | On the lock question - running sbt ~fastLinkJS followed by starting Vite fails for me for the same lock issue that you mentioned. I'm not using the plugin, but my setup is equivalent. I also wasn't aware of the SBT_SERVER_FORCESTART option, so I'd typically just start the Vite server first and queue the sbt session afterwards. | 04:54:43 |
| nikitaga | Huh. What about running SBT ~fastLinkJS in one tab, and running the auto-reloading backend server via sbt in another tab, does that not work either on Windows? I don't think I've ever run into this error on macros, doing all kinds of things. | 04:58:56 |
| nikitaga | * Huh. What about running SBT ~fastLinkJS in one tab, and running the auto-reloading backend server via sbt in another tab, does that not work either on Windows? I don't think I've ever run into this error on macos, doing all kinds of things. | 04:59:24 |
| granarder | Nah, that doesn't work either for me. I'm always running these commands in separate terminals anyway. | 05:00:08 |
| granarder | If the terminal running sbt ~fastLinkJS is the one that is unable to acquire the lock (i.e. if it attempts to get the lock while the command to start Vite is grabbing the sbt output directory for your JS files), then sbt gives you a prompt that allows you to start a new server instead of just failing. I've not looked into whether there's an option you could provide to sbt to always do that though (outside of the env var you mentioned). | 05:04:40 |
 Scalable Cucumber joined the room. | 12:17:28 | |
| 2 Jun 2024 | ||
 heko_ joined the room. | 11:17:34 | |
| 3 Jun 2024 | ||
 bluxwarrior_66894 joined the room. | 01:23:50 | |
 kike jovel joined the room. | 04:51:04 | |
 lrytz changed their profile picture. | 12:22:25 | |
 quafadas | As a follow up to this, I did the detail grind on this idea, the test suite is now a lot more polished, and I think it is useable by someone who is "not me". If this takes longer than 20 second or so, then I guess it needs more polish! | 18:10:52 |