Unable to run the wasp locally
This is the doc I have been following to setup the server locally. https://github.com/wasp-lang/wasp/tree/main/waspc#quick-overview
I have been able to fix the issues faced untill now, but when I am trying to run the example app I am facing errors. I have attached the image for reference.
Thank you.
GitHub
wasp/waspc at main · wasp-lang/wasp
The fastest way to develop full-stack web apps with React & Node.js. - wasp-lang/wasp
2 Replies
Hi @TylerDurden. 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, but the knowledge sources you provided do not include the attached image you referenced, so I cannot review the specific error message you're encountering.
However, based on common issues reported when running Wasp example apps locally, here are a few troubleshooting steps that might help:
1. Node.js Version: Make sure you are using a supported Node.js version. Wasp typically recommends Node 18.x (LTS), and there have been issues reported with Node 20.x or other versions not working as expected with some Wasp projects. Double-check your Node version with
node -v and switch to Node 18 if needed Getting Started Issues.
2. Docker Requirement: If your app uses a PostgreSQL database (the default for many Wasp examples), Docker must be installed and running on your system, as Wasp uses Docker to manage the dev database. If you see errors about not being able to connect to the database or missing Docker, install Docker Desktop and ensure it is running before starting your app. Then, run wasp start db to start the database, followed by wasp start to run the app Need help running Wasp app.
3. Permissions Issues: On Mac or Linux, if you see errors like EACCES: permission denied, this usually means you don't have the necessary permissions for some directories (often node_modules). Try running the command with elevated permissions (e.g., sudo), or fix the directory permissions Wasp start.
4. Cleaning the Project: If you encounter errors about missing modules (e.g., Cannot find module 'wasp/server'), try running wasp clean to remove generated files and dependencies, then wasp start again to rebuild everything Hey! Any ideas on some solutions to these errors?.
If you can provide the specific error message (by pasting the text or describing it), I can give more targeted advice. Otherwise, please try the steps above, as they address the most common issues when running Wasp example apps locally.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @TylerDurden, 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?Sure, works!