Node version conflict between wasp and astro
As title, Wasp and astro has node dependency conflict.
Any ideas? It seems like I have to degrade astro to fit the lower node version. Or I have to move blog parts to make it an individual project.
8 Replies
use NVM and then run
nvm use 18 when working on Wasp
we are upgrading the node requirements in Wasp in the new release (coming soon 👀 )freeCodeCamp.org
Node Version Manager – NVM Install Guide
In this article, I'll explain how you can install NVM, or Node Version Manager, on Windows, Linux, and Mac. What is NVM? Node Version Manager (NVM), as the name implies, is a tool for managing Node versions on your device. Different projects on your device may be using different versions
This a solution for dev. However I still have the version conflict in deployment. Looking forward to the update.
Wohooo @Tempest, you just became a Waspeteer level 1!
Can you tell us a bit more about the conflict in deployment? How are you deploying -> I am a bit surprised you have a conflict there, since Astro should be static pages (right @Vinny (@Wasp) ?), so no node should be needed.
true. I've never encountered this error
How are you deploying Astro? can you share the error you get @Tempest ?
NVM, I won't get the conflict after building the blog. It gets a node conflict error when I run "npm run dev". > docs@0.0.1 build
astro check && astro buildNode.js v18.12.0 is not supported by Astro! Please upgrade Node.js to a supported version: ">=18.14.1"
AH so it happens during development, got it! Yeah that makes sense, at that point astro si running via dev server.
Update coming any moment though, so this will be thing of the past!