Error after upgrading to Wasp 0.15.0
Hey Wasp team!
I just upgraded Wasp from v0.14.0 to v0.15.0 by following all the steps on the migration guide (https://wasp-lang.dev/docs/migration-guides/migrate-from-0-14-to-0-15).
After upgrading, my project doesn't seem to build anymore, I am now getting following error:
I have already tried
wasp clean and reinstalling dependencies, without any luck.
Any ideas on how to resolve this?Migration from 0.14.X to 0.15.X | Wasp
What's new in 0.15.0?
4 Replies
Wohooo @WWWillems, you just became a Waspeteer level 5!
Hi @WWWillems. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Thank you for your question about the error you're encountering after upgrading to Wasp 0.15.0. Based on the information provided in the knowledge sources, I don't have specific details about this particular error. However, I can offer some general troubleshooting steps that have helped resolve similar issues in the past.
1. First, ensure you're using the correct Node.js version. Wasp 0.15.0 might have specific Node.js version requirements. Try using Node.js 18 if you're not already, as mentioned in one of the support threads: Discord support thread: Error building after migrating Wasp to 0.12 > Answers Part 3 (https://discord.com/channels/686873244791210014/1212533517360177253).
2. You mentioned you've already tried
wasp clean, but it's worth trying the full sequence again:
- Run wasp clean
- Delete the node_modules folder
- Run wasp start
This combination has helped resolve similar issues for other users, as mentioned in Discord support thread: Hey! Any ideas on some solutions to these errors? > Answers (https://discord.com/channels/686873244791210014/1215750573278629958).
3. Check your imports, especially in server-side files. Make sure you're not accidentally importing client-side modules on the server. The error message suggests there might be an issue with type definitions, which could be related to incorrect imports.
4. If the problem persists, it would be helpful to share more details about your project structure, particularly the content of the ext-src/server/types.ts file where the error is occurring.
5. As a last resort, you might want to consider creating a new Wasp project with version 0.15.0 and gradually moving your code over to isolate the issue.
If these steps don't resolve the issue, I recommend reaching out to the Wasp team directly through their Discord channel or GitHub issues, as this seems to be a specific problem that might require more in-depth investigation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @WWWillems, 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?I have a few usages of
Prisma.validator in my project, could this be related?Could you share your
server/types.ts content so we can take a closer look? Or any piece of code that gives you errors 🙂