Issue with dotenv
-- [Error] Your wasp project failed to compile: -------------------------------
- Error: Dependency conflict for user dependency (dotenv, ^16.0.2): Version must be set to the exactly the same version as the one wasp is using: ^16.0.3
❌ --- [Error] Compilation of wasp project failed: --------------------------------
1 errors found
usr/Projects/revsion_ai/revision_ai/app$ wasp db migrate-dev
🐝 --- Compiling wasp project... --------------------------------------------------
❌ --- [Error] Your wasp project failed to compile: -------------------------------
- Error: Dependency conflict for user dependency (dotenv, ^16.0.3): Version must be set to the exactly the same version as the one wasp is using: ^16.0.2
❌ --- [Error] Compilation of wasp project failed: --------------------------------
1 errors found
3 Replies
Hi @ArDev. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
It seems like you're experiencing a dependency conflict with the
dotenv package. Wasp requires that user dependencies match exactly with the versions it uses. In your case, Wasp is using dotenv version ^16.0.2 and your project is using version ^16.0.3.
To resolve this issue, you should adjust your package.json file to match the dotenv version that Wasp is using. Here's how you can do it:
1. Open your package.json file.
2. Find the dotenv dependency.
3. Change its version to ^16.0.2.
4. Save the file and run npm install or yarn install to update your node_modules.
This should resolve the dependency conflict and allow your Wasp project to compile successfully.
This issue is related to the way Wasp handles dependency version checking, as discussed in this Github issue (https://github.com/wasp-lang/wasp/issues/1859). Wasp currently requires that user dependencies match exactly with the versions it uses to avoid conflicts. However, this approach can sometimes lead to false positives in the version conflict check.
Please note that the Wasp team is considering allowing users to specify some NPM dependency versions themselves, as discussed in this Github issue (https://github.com/wasp-lang/wasp/issues/645). This could potentially alleviate such issues in the future.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @ArDev, 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?@ArDev did you resolve this one? So error messsages says exactly what you need to do
yeah just didnt need the package itslef