Getting this issue in WASP 0.16.2
Client ] > [email protected] start
[ Client ] > vite
[ Client ]
[ Server ] > [email protected] watch
[ Server ] > nodemon --exec 'npm run bundle-and-start exit 1'
[ Server ]
[ Server ] [nodemon] 2.0.22
[ Server ] [nodemon] to restart at any time, enter
rs
[ Server ] [nodemon] watching path(s): src//* ../../../src//* .env
[ Server ] [nodemon] watching extensions: ts,mts,js,mjs,json
[ Server ] [nodemon] starting `npm run bundle-and-start exit 1
[ Client!] failed to load config from /Users//wasupupdate/my-saas/app/.wasp/out/web-app/vite.config.ts
[ Client!] error when starting dev server:
[ Client!] Error: Cannot find module @rollup/rollup-darwin-arm64. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try npm i` again after removing both package-lock.json and node_modules directory.
[ Client!] at requireWithFriendlyError (/Users//wasupupdate/my-saas/app/node_modules/vitest/node_modules/rollup/dist/native.js:63:9)
[ Client!] at Object.<anonymous> (/Users//wasupupdate/my-saas/app/node_modules/vitest/node_modules/rollup/dist/native.js:72:76)
[ Client!] at Module._compile (node:internal/modules/cjs/loader:1469:14)
[ Client!] at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
[ Client!] at Module.load (node:internal/modules/cjs/loader:1288:32)
[ Client!] at Module._load (node:internal/modules/cjs/loader:1104:12)
[ Client!] at cjsLoader (node:internal/modules/esm/translators:346:17)
[ Client!] at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:286:7)
[ Client!] at ModuleJob.run (node:internal/modules/esm/module_job:234:25)
[ Client!] at async ModuleLoader.import (node:internal/modules/esm/loader:473:24)
app %GitHub
Issues · npm/cli
the package manager for JavaScript. Contribute to npm/cli development by creating an account on GitHub.
10 Replies
Hi @Zuck. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It looks like you're encountering a dependency issue with Vite in your Wasp project. This error is related to a known npm bug with optional dependencies.
The error message is quite clear about what's happening:
This is a common issue that can occur when npm doesn't properly handle optional dependencies. The error is happening in the Vite configuration loading process.
How to fix it:
1. First, try the solution suggested in the error message:
- Delete the
package-lock.json file in your project
- Remove the node_modules directory
- Run npm install again
- Then try wasp start again
2. If that doesn't work, try running wasp clean first, which will clean up the generated files, and then start again with wasp start.
3. Make sure you're using a compatible Node.js version. Wasp requires the latest Node.js LTS version, which is currently Node.js 18 as mentioned in the documentation.
4. If you're using a custom Vite configuration, make sure it's properly set up. Wasp allows you to customize the Vite config by editing the vite.config.ts file in your project root directory as described in the documentation.
These types of dependency issues are sometimes related to npm version mismatches or conflicts. Wasp has moved from Webpack to Vite for better performance, but occasionally these types of dependency issues can occur, especially when there are npm bugs involved.
Let me know if these steps help resolve your issue!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Zuck, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai I tried fix 1, it worked but gave some type errors then when I fixed those and restarted wasp it gave the same error
Let me check the knowledge base for you again. One moment! :books:
----------------------
I understand you're still facing issues with your Wasp project. Let's try a more thorough approach to resolve this persistent error.
Based on the knowledge sources, when users encounter persistent errors like yours, a more comprehensive cleanup might be needed. Here are some steps to try:
1. Run
wasp clean to completely remove the generated files:
This will remove all the .wasp directory and node_modules, giving you a fresh start as mentioned in the Discord support thread.
2. After cleaning, start your app again:
3. If you're still seeing type errors related to modules like wasp/server or wasp/entities, this could be because the Wasp compiler needs to generate the SDK for you to have all the wasp/* packages as noted in another Discord thread.
4. If you're working in a WSL or similar environment, sometimes path resolution can cause issues. Make sure you're running the commands from the correct directory.
5. In some cases, network issues can cause npm installation problems. If you suspect this might be the case, try running the commands again when you have a stable connection as mentioned in one of the Discord threads.
6. Avoid manually editing any files in the .wasp directory as these are automatically generated and will be overwritten when you run wasp start again as noted in the database URL support thread.
If you're still encountering issues after these steps, could you share the specific type errors you're seeing? That would help narrow down the problem further.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Zuck, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai I tried fix 1, it worked but gave some type errors then when I fixed those and restarted wasp it gave the same error
Let me check the knowledge base for you again. One moment! :books:
----------------------
I see you're still encountering the same error after trying the first fix. This sounds like a persistent issue that might be related to a double installation problem or dependency conflicts in your Wasp project.
Based on the knowledge sources, this could be similar to the double React installation issue mentioned in GitHub issue #1640, where there are conflicts between different installations of the same package.
Let's try a more thorough approach:
1. First, try a complete cleanup with:
This will remove all the
.wasp directory and node_modules folders, giving you a truly fresh start.
2. If you're using the SaaS template or a complex project, there might be specific dependency issues. Some users have reported that after cleaning, they needed to:
before starting the app again.
3. If the error persists, it could be related to how npm resolves dependencies. One user in the Discord threads mentioned that deleting the app folder and putting in a fresh copy from a new wasp new command helped resolve similar issues.
4. Another possibility is that there's a conflict between your local npm environment and the one Wasp is using. Make sure you're using a compatible Node.js version (v18 is recommended for Wasp).
5. If you're still seeing the Rollup/Vite error specifically, it might be worth checking if there's an issue with the Vite cache. Some users have reported that clearing the Vite cache helped resolve similar issues.
If none of these solutions work, could you share the specific type errors you encountered? That might provide more clues about what's happening in your specific case.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Zuck, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?this feels like a deep break
I think its only on m1 macs not sure
wait its happening on 16.0 too
im so confused
wasp clean + delete package-lock.json?
ya that was essentially it hahah @miho
i tried fixing other ways and that broke more but i reset everything and did that and that was the solve
Yep, it's a weird npm related bug we have seen in the wild
Cool. I set this to solved!