Issues with upgrading wasp project to v15
I'm trying to update my wasp project up to 0.15.1, the same version I'm currently running on my machine, but whenever I attempt any wasp command (wasp db start or wasp start), I get an error:
I've already run wasp clean, and have changed my wasp version in my main.wasp file to be 0.15.1
11 Replies
Hi @CamBlackwood. 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 experiencing an issue with Prisma version compatibility when upgrading your Wasp project to version 0.15.1. This is a common issue that can occur during Wasp upgrades or when there's a mismatch between Prisma versions.
Based on the error message, Wasp is expecting Prisma version 5.19.1 in your package.json, but it's finding a different version. Here are a few steps to resolve this:
1. First, make sure you've run
wasp clean (which you've already done, good!)
2. Check if there's a package.json file in any parent directory of your Wasp project. This can cause issues as Prisma might pick up the wrong version from there:
This is a known issue in Wasp where if you have a package.json file in a parent directory with a different Prisma version, it can interfere with your project Github Issue (open): If there is package.json above the Wasp project, prisma version from it will be used.
3. Try running wasp db migrate-dev to regenerate the Prisma client with the correct version.
4. If that doesn't work, you might need to manually ensure the correct Prisma version is installed. You can try:
- Going into your project's .wasp/out/ directory
- Running npm install [email protected]
Another user had a similar Prisma-related issue and resolved it by running wasp clean followed by wasp start Discord support thread: (Resolved) Prisma Error on Mac.
If these steps don't resolve your issue, you might want to try completely reinstalling Wasp to ensure you have a clean installation of version 0.15.1.
Let me know if this helps!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @CamBlackwood, 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 none of those steps worked this time unfortunately. I'm stuck for now
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm sorry to hear that none of the suggested steps worked for your Prisma version issue. This is indeed a frustrating situation.
Based on the knowledge sources, there are a few more things you could try:
1. Check if you have a
package.json and package-lock.json not just in parent directories, but also in your home directory. One contributor mentioned:
Github Issue (open): If there is package.json above the Wasp project, prisma version from it will be used
2. Try manually modifying the Prisma client import path in your project. One user found success by changing:
After this change, wasp start worked for them Github Issue (closed): Investigate Prisma client initialization error on first start after clean
3. Try running npx prisma generate --schema ../db/schema.prisma from within your .wasp/out/server directory to manually generate the Prisma client.
If none of these solutions work, you might be encountering a deeper issue with Wasp and Prisma compatibility. In that case, it might be worth:
1. Filing an issue on the Wasp GitHub repository
2. Temporarily downgrading to a previous version of Wasp that worked for your project
3. Creating a new project with Wasp 0.15.1 and gradually migrating your code over
The Wasp team is aware of various Prisma-related issues and is working on improvements to how Wasp handles Prisma operations.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @CamBlackwood, 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 what’s the simplest way of me downgrading my wasp version?
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on your question about downgrading Wasp, here's how you can do it:
The simplest way to downgrade your Wasp version is to use the installer script with a specific version flag. You can run:
Where
VERSION_NUMBER is the specific version you want to downgrade to (for example, 0.11.8, 0.12.0, etc.).
This approach is mentioned in the Wasp installer script, which supports installing specific versions rather than just the latest one GitHub Issue: Installation failed.
After installing the older version, you'll also need to:
1. Update the Wasp version in your project's main.wasp file to match the version you've downgraded to (for example, change "^0.15.1" to "^0.12.0")
2. Run wasp clean in your project directory to clear any cached files
3. You might need to adjust your project structure if you're downgrading across major versions (like from 0.15 to 0.11), as there have been significant structural changes between some versions
If you're experiencing issues with a specific version, you might want to try version 0.11.8 which was noted as working in one of the support threads Discord support thread.
Remember that downgrading might require additional adjustments to your code if you've been using features that aren't available in the older version.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @CamBlackwood, 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?@CamBlackwood what was the Prisma version you had in
package.json when you encountered that initial error message?Then the error message was expected 🙂 Wasp is using Prisma 5 since 0.15.0, check the migration docs https://wasp.sh/docs/migration-guides/migrate-from-0-14-to-0-15
Migration from 0.14.X to 0.15.X | Wasp
What's new in 0.15.0?
ahh, sorry didn't realise about the migration docs (tbh, I forgot I needed to do a migration process for a new version)! Not sure how easy it would be to implement but could they be linked in the error somehow?
I think it would be quite unpractical to keep track of which features we added when and to be able to include them in the error message :sadboi: best we can do is manual labor like this 😄
hahah, very true!