Gatsby Incorrectly Detecting Node.js v16.13.0 Instead of Installed v20.17.0 #39080
Open
2 tasks done
Labels
status: triage needed
Issue or pull request that need to be triaged and assigned to a reviewer
type: bug
An issue or pull request relating to a bug in Gatsby
Preliminary Checks
Issue Description
I am encountering a problem with Gatsby while trying to start a project. I get an error "Gatsby requires Node.js 18.0.0 or higher (you have v16.13.0)" when running npm run develop. Despite having the recent version of nodejs installed, Gatsby seems to be detecting Node.js v16.13.0, which I don't even have installed on my machine.
Steps Taken So Far
node -v
, which returns v20.17.0.nvm ls
, and it only lists v20.17.0.where node
to check for conflicting Node.js versions but couldn’t find any installation of v16.13.0.gatsby clean
and reinstalled all dependencies (npm install
).Additional Information
PATH
environment variables are pointing to the correct Node.js installation.Could this be a cached environment issue? Are there any other places where Gatsby could be picking up this outdated version of Node.js?
Reproduction Link
private repo
Steps to Reproduce
Expected Result
Gatsby should detect and use Node.js v20.17.0 when running the project.
Actual Result
Gatsby is still showing the following error: Gatsby requires Node.js 18.0.0 or higher (you have v16.13.0)
However, I do not have Node.js v16 installed, and I am running Node.js v20.17.0.
Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: