New SaaS app Bug?
Hey so when I try to run
wasp new
Then select 3 (saas)
I run db start works fine, when I then run wasp start I get this error
I changed apexcharts to 4.3.0 I ran it again but I got another error...
I tried doing this with 2 node versions using nvm (20.11.1 & 23.5.0)
16 Replies
Hi @fustuk.. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, I can offer some insights about your issue with creating a new SaaS app using Wasp. However, it's important to note that the specific error you're encountering isn't directly addressed in the given documents. Let me provide you with the relevant information I can extract:
1. Node.js Version Compatibility:
Wasp currently requires Node.js version 18. The versions you mentioned (20.11.1 and 23.5.0) are not officially supported yet. As stated in a Discord support thread (https://discord.com/channels/686873244791210014/1197484972668375101), Wasp is planning to update its Node.js version requirements soon to include versions >= 18, but this hasn't been implemented yet.
2. Recommended Solution:
The recommended approach is to use Node.js version 18 with Wasp. You can use nvm (Node Version Manager) to switch to the correct version. As mentioned in another Discord thread (https://discord.com/channels/686873244791210014/1195126418321981470), you should use
nvm use 18 to switch to Node.js 18 before running Wasp commands.
3. Upcoming Changes:
The Wasp team is aware of the Node.js version restriction and is working on updating it. According to a GitHub issue (https://github.com/wasp-lang/wasp/issues/1618), they plan to upgrade the Node version requirement to 20 in the future.
4. Additional Troubleshooting:
If you continue to experience issues after switching to Node.js 18, you might want to try the following steps:
- Run wasp clean before wasp start
- Check if there are any specific error messages related to database connections or other dependencies
Unfortunately, the knowledge sources don't provide information about the specific error you're encountering with apexcharts or any other detailed error messages. If the problem persists after switching to Node.js 18, I recommend reaching out to the Wasp community on their Discord channel or creating a GitHub issue with the exact error messages you're seeing.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @fustuk., 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?My previous project was using 20.11.1 so I dont think the issue is on my end, has any dependency version been updated recently @kapa.ai
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the information provided in the knowledge sources, I can offer some insights regarding your question about dependency versions and Node.js compatibility:
1. Recent Node.js Support Update:
According to a recent Discord thread (https://discord.com/channels/686873244791210014/1219009534174167101), Wasp has updated its Node.js requirements with version 0.12. The current documentation now states that Wasp supports Node.js versions 18 and above. This means that your Node.js version 20.11.1 should be compatible with the latest version of Wasp.
2. Potential Polyfill Issue:
There was a recent issue reported in a GitHub issue (https://github.com/wasp-lang/wasp/issues/1833) where Wasp's server would break when using Node.js 20 due to a Web Crypto API polyfill. This issue was specific to Wasp 0.12 and Node.js 20. The Wasp team was working on a fix for this, but I don't have information on whether it has been resolved yet.
3. Dependency Updates:
The knowledge sources don't provide specific information about recent dependency updates. However, given that you mentioned changing the version of apexcharts, it's possible that there might be some compatibility issues with certain dependencies.
4. Recommendation:
Since your previous project was working with Node.js 20.11.1, and Wasp now officially supports Node.js versions 18 and above, the issue might not be related to the Node.js version. It could be due to a specific dependency or a recent change in Wasp itself.
To troubleshoot further, I recommend:
- Ensure you're using the latest version of Wasp
- Try creating a new project without modifying any dependencies to see if the issue persists
- If the problem continues, it would be helpful to share the exact error messages you're encountering with the Wasp team, either through their Discord channel or by creating a GitHub issue
Unfortunately, the knowledge sources don't provide enough information to determine if there have been any specific dependency updates that might be causing your issue. If you need more detailed information, I suggest reaching out to the Wasp community directly for the most up-to-date information on recent changes and known issues.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @fustuk., 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?
alright so I had to update the cli, and change nvm to 20.11.1 (23.5 didnt work)
Seems like it is resolved!
@Vinny (@Wasp) I guess this is the same problem we fixed with the updated deps in the template?
Now that I updated the cli my old projects throw this error :/
And after I update package.json I get this, how do I upgrade an existing project to support new cli version @miho
You can update the required Wasp version in the
main.wasp to be ^0.15.0got it, thanks!
And do you know where these errors come from ? react-router-dom methods deprecated or smth
Wohooo @fustuk., you just became a Waspeteer level 9!
I fixed the previous error but I am stuck on this @miho I cant route to any page inculding /login just getting 401 and nothing happening... everything was working before updating the cli
What does the CLI say? Does the server report any errors?
Did you follow the migration guide? https://wasp-lang.dev/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?
no I did not thank you, adding <Outlet/> instead of children in App.tsx fixed it
noice