Opensaas with new wasp version failed to install dependencies
Hello guys. I am starting a new project and of course using our beloved opensaas template and wasp, but it fails to install the dependencies for what I could see from the logged errors. I tried to used the npm I --force to see if I could overcome it but when I tried to migrate the db in order to start the app it fails again because it tries to install the dependencies. I am assuming it's something with the dependency version or related because of the error I got.
11 Replies
Hi @Stefan Vitória. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry to hear that you're having trouble with the OpenSaas setup. Based on the knowledge sources provided, there could be a few things causing this issue.
1. Node.js version: Wasp requires a specific version of Node.js. If you're using a version that's not compatible, you might encounter issues. For example, one user reported an error when trying to use Node.js 19.9.0, but Wasp required Node.js 18.12.0 at the time (source (https://github.com/wasp-lang/wasp/issues/1194)). Make sure you're using a compatible version of Node.js.
2. Insufficient resources: If your system doesn't have enough resources (like RAM), it might fail to install dependencies. One user reported a similar issue and found that their VPS only had 512MB of RAM, which was causing the problem (source (https://discord.com/channels/686873244791210014/1213593156646604820)).
3. Manual installation: If automatic installation fails, you could try manually installing the dependencies. One suggestion was to run
wasp compile, then manually run npm install in the .wasp/out/web-app and .wasp/out/server folders (source (https://discord.com/channels/686873244791210014/1213593156646604820)).
If none of these suggestions work, it might be helpful to provide more detailed logs or error messages. This could help identify the specific issue causing the installation to fail.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Stefan Vitória, 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 is when i run the wasp db migrate-dev
I actually ended up upgrading de zod version and it worked fine. But was it a breaking changing that provoke it or...
I think the openai package and the installed zod were incompatible for some reason.
Exatly. But since those were the version on the opensaas package.json i decide to inform here, I wasn't sure why it was happening. But I updated the zod package and it was ready to go.
@Vinny (@Wasp) @martinsos we should probably update the versions in the template then
is problem fixed?
Wohooo @Mitu, you just became a Waspeteer level 1!
@Stefan Vitória
In a few minutes, it'll be fixed 🙂
Fixed 😄
Yeah, in my case I updated the versions
so @kapa.ai , what if i want to install a specific version of wasp?
Let me check the knowledge base for you. One moment! :books:
----------------------
To install a specific version of Wasp, you can use the installer script with the
-v option followed by the version number. Here's an example of how to do it:
Replace x.y.z with the version number you want to install. For example, to install version 0.12.0, you would run:
You can check the list of valid versions, including the latest one, on the Wasp GitHub releases page (https://github.com/wasp-lang/wasp/releases) (source (https://wasp-lang.dev/docs/general/cli#miscellaneous-commands)).
If you want to switch to the latest version of Wasp, you can do so with the following command:
This will install the latest version of Wasp on your system.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Stefan Vitória, 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?