Filip Sodić

That's a good question. I consider that very high in priority because most of our project structure discussions reach a point where we say "we might get that with NPM...

User hitting this: https://discord.com/channels/686873244791210014/1374829396929548408/1375183950967869581

@infomiho Do we have an issue for that parallelization? I can't find it. I'll create one if not. If that draft PR is ready, can we only run it on...

Check if it got fixed by #1769

Hey @Rotemoyal, thanks for letting us know! It's not ideal, but you should be able to fix it by running `wasp clean` after any command throws this error, and then...

Hmm, strange, must be something else then. What happens when you run `npm --version`?

> maybe it worth checking if npm exists so the error message will be indicative? Definitely! I just made a new issue to track it: https://github.com/wasp-lang/wasp/issues/2113 Thanks for letting us...

> Getting this issue too Did you the suggested solution: https://github.com/wasp-lang/wasp/issues/1980#issuecomment-2183976395

@hellwaiver Good thing you did :) It helps knowing how many people run into it. Thanks!

Seems it's not as bad as I thought. > Essentially, the compiler needs to run at least once while the declaration points to a non-existing implementation. If this were true,...