[ Server ] Starting npm installwasp-bin: npm: streamingProcess: chdir: invalid argument (Bad file de
suddenly, when i run I get this error:
6 Replies
Hi @prof_mark. 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 don't have enough specific details to directly address the exact error message you're encountering. However, I can suggest a few troubleshooting steps that might help resolve similar issues:
1. Update Wasp: Try updating Wasp to the latest version using the following command:
This suggestion comes from a Discord support thread here (https://discord.com/channels/686873244791210014/1212533517360177253).
2. Check file permissions: The error message suggests there might be a file descriptor issue. This could be related to file permissions. Make sure you have the necessary permissions to access and modify files in your project directory.
3. Increase file limit: If you're encountering issues related to too many open files, you might try increasing the file limit. A user in the Discord thread mentioned using:
to bypass a similar error here (https://discord.com/channels/686873244791210014/1212533517360177253).
4. Check Node.js version: Ensure you're using a compatible Node.js version. Wasp has specific Node.js version requirements. According to the Github issue (https://github.com/wasp-lang/wasp/issues/1194), Wasp requires Node.js ^18.12.0.
If these steps don't resolve the issue, you might need to provide more context about your setup, such as your operating system, Node.js version, and Wasp version, to get more specific help.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @prof_mark, 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?
Have you used
wasp before successfully or this happened right after the installation?Also does
wasp clean help?ah sorry for not following up - yes did the trick!
@prof_mark it would still be great to understand what caused this, do you have any idea? Did you migrate to newer versino of Wasp? Or anything else taht could have caused this?
I had recently migrated but it did work after the migration, then failed again
I am not sure, but I suspect it could have been due to messing around with my docker images. I was working on something else and deleted all the docker images though docker desktop, so maybe wasp lost a ref? And then clean fixed it?