Bug?: `wasp start` reinstalls dependencies after stopping
When I make a change with wasp and everything is OK, it immediately recompiles without any problem.
When I make a change and something is wrong, it gives me the error, I fix it and it recompiles again without any problem.
The problem is when it tries to compile something that is wrong, so it gives me back correctly an:
But it immediately starts to recompile:
Then I stopped the process and used
This only ever happens to me exactly in this scenario (I try to avoid stopping the process at that point), but why does it happen? If everything is installed, why does it take the same time as if I install everything again?
When I make a change and something is wrong, it gives me the error, I fix it and it recompiles again without any problem.
The problem is when it tries to compile something that is wrong, so it gives me back correctly an:
❌ --- [Error] Recompilation on file change failed.: ------------------------------
1 errors found.
❌ --- [Error] Your wasp project failed to compile: -------------------------------
- SDK build failed with exit code: 2But it immediately starts to recompile:
❌ --- [Error] Recompilation on file change failed.: ------------------------------
1 errors found
❌ --- [Error] Your wasp project failed to compile: -------------------------------
- SDK build failed with exit code: 2
🐝 --- Recompiling on file change... ----------------------------------------------Then I stopped the process and used
wasp start❌ --- [Error] Recompilation on file change failed.: ------------------------------
1 errors found
❌ --- [Error] Your wasp project failed to compile: -------------------------------
- SDK build failed with exit code: 2
🐝 --- Recompiling on file change... ----------------------------------------------
^C
rootall@Nerox-LpTp:~/apps/minisaas-boilerplate/app$ wasp start
🐝 --- Starting compilation and setup phase. Hold tight... ------------------------
🐝 --- Compiling wasp project... --------------------------------------------------
[ Wasp ] Starting npm install
[ Wasp ]
[ Wasp ] added 1 package, and audited 844 packages in 3s
[ Wasp ]
[ Wasp ] 140 packages are looking for funding
[ Wasp ] run for details
[ Wasp ]
[ Wasp ] 9 vulnerabilities (2 low, 3 moderate, 4 high)
[ Wasp ]
[ Wasp ] To address issues that do not require attention, run:
[ Wasp ] npm audit fix
[ Wasp ]
[ Wasp ] To address all issues (including breaking changes), run:
[ Wasp ] npm audit fix --force
[ Wasp ]
[ Wasp ] Run for details.
[ Client ] Starting npm install
[ Server ] Starting npm install
[ Server ] Still installing npm dependencies!
[ Client ] Still installing npm dependencies!
[ Server ] Installation going great - we'll get there soon!
[ Client ] Installation going great - we'll get there soon!
[ Server ] The installation is taking a while, but we'll get there!
[ Client ] The installation is taking a while, but we'll get there!
[ Client ] Yup, still not done installing.
[ Server ] Yup, still not done installing.
[ Server ] We're getting closer and closer, everything will be installed soon!
[ Client ] We're getting closer and closer, everything will be installed soon!This only ever happens to me exactly in this scenario (I try to avoid stopping the process at that point), but why does it happen? If everything is installed, why does it take the same time as if I install everything again?
