wasp 0.16.5 Problem
after the last issue with @tanstack/react-query , i updated my wasp version from 0.16.3 to 0.16.5.
i run wasp clean , and deleted all package-lock.json and node_modules , deleted database container and volume and started fresh :
everything seem to run correctly except that the dev server doesnt start , the process quits after saying Starting up generated project ,here is the log:
10 Replies
Hi @Dada. 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 in the knowledge sources, your Wasp project appears to compile and set up successfully, but the dev server process exits right after "Starting up generated project..." with no further output or error.
Here are some possible causes and troubleshooting steps, based on similar issues reported by other users:
1. Resource Constraints (RAM/CPU):
- On low-resource environments (like VPS or small EC2 instances), Wasp processes (especially npm install or TypeScript compilation) can be killed silently due to insufficient memory. Users have reported that 512MB or even 1GB RAM may not be enough for Wasp to run reliably, and processes may be killed without clear error messages. Consider increasing your server's RAM if possible, or monitor system logs (e.g.,
dmesg or /var/log/syslog) for "Out of memory" or "Killed process" messages during startup. This was a common cause for silent failures on VPS and cloud instances, as seen in this Discord thread and here.
2. Port Conflicts:
- Ensure that ports 3000 (frontend) and 3001 (backend) are not already in use by other processes. If another service is using these ports, Wasp's dev server may fail to start and exit silently. You can check for running services on these ports and terminate them if necessary, as suggested here.
3. Prisma Client Generation Issues:
- Sometimes, after a wasp clean, the Prisma client may not be generated correctly, leading to silent server crashes. You can try manually running:
Then try wasp start again. This was a known issue in earlier Wasp versions and may still occur in edge cases as discussed here.
4. Check for Errors in Logs:
- If the process exits without error, try running the backend server directly to see if any errors are output:
This may reveal missing dependencies or runtime errors not shown by the Wasp CLI.
5. Node Version Compatibility:
- Ensure you are using a Node.js version compatible with Wasp (typically Node 18 or 20). Incompatible Node versions can cause subtle issues as mentioned here.
If none of these steps reveal the issue, please provide any additional logs or error messages you see when running the backend server directly. The knowledge sources do not contain a definitive solution for your exact scenario, but these are the most common causes for the symptoms you described.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Dada, 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?Hey I commented in another thread!
What if you use 0.16.3 or 0.16.4? Check
wasp version on how to install it.
What if you create new app?i have the @tanstack/react-query error with the older version , thats why i updated the new version
Let's talk here! That error is gone in all wasp versions so feel free to try 0.16.3 again
I was seeing this yesterday too after trying wasp for the first time. Glad to see im not alone. Will try the new version
Was it react-query error for you or something else?
it was also react-query
i just initialized a new project and am no longer seeing the error now though
Ok great, that one was solved. It actually wasn't error in wasp, it was caused by latest version of react-query being broken. They fixed it now, so all wasp versions now work ok
gotcha makes sense. I did see react-query had a new release like 2 days ago but I wasn't sure that was the issue since i thought wasp was locking the version of react-query. I didn't think that new version was being used
We lock the major version but allow minor and patch both for security updates and minor improvements. But then there is risk of bugged releases like this one. Solution is probably not to lock the version completely, we don't want to deorive users of potentially critical security updates, but to offer a way to specify older version if new one is broken - we will be looking how to offer more flexibility there. In theory this should never happen, wasp relies heavily only on a couple very famous npm packages, but there it is, even they make mistakes.