You need to have
npm) installed on your machine and available in
You can check
npm versions by running:
node -vnpm -v
We recommend using nvm for managing your Node.js installation version(s).
Quick guide on installing/using nvm
Install nvm via your OS package manager (aptitude, pacman, homebrew, ...) or alternatively via nvm install script.
Then, install a version of node that you need, e.g.:
nvm install 16
Finally, whenever you need to ensure specific version of node is used, run e.g.
nvm use 16
to set the node version for current shell session.
You can run
to check the version of node currently being used in this shell session.
Check NVM repo for more details: https://github.com/nvm-sh/nvm .
Why does Wasp require this specific
node range and doesn't support a newer version x.y.z?
At Wasp, we focus on supporting the latest LTS ("long-term-support") Node.js version, since it guarantees stability and active maintainance, which is why the official Node.js team recommends it for usage in production. Therefore, a specific Wasp release will usually require the version of Node.js that was LTS at that point of time. Check out https://nodejs.org/en/about/releases/ for more details about Node.js releases.
Sometimes we will make an exception to that and additionally limit the Node.js version or postpone switching to the latest LTS if there are certain issues with new Node.js version, in which case we will catch up once those are resolved on Node.js side or we find a workaround on Wasp side.
- Linux / OS X
- From source
wasp new MyNewApp # Creates a new web app named MyNewApp.cd MyNewAppwasp start # Serves the web app.
That's it 🎉! You have successfully created and served a new web app at http://localhost:3000 and Wasp is serving both frontend and backend for you.
Check out the 🤓 Todo App tutorial 🤓 , which will take you through all the core features of Wasp!
You can also: