Deployment issue with node version in Gatsby starter
20 repliesLast updated: Jan 4, 2023
Hello everyone!, has anybody encountered an error in deployment regarding the node version of your repository? according to my logs, Im using a previous version of node rather than the latest (18.12.1 Lts). With this i cannot deploy. I've checked in my terminal and it returns that iI have the most updated version installed in my desktop. Not sure what to do here. Any help will be much appreciated!
Hello user E 👋Could you share a bit more about the deployment issue you’re experiencing?
Hi user J 🙋♀️, yeah. I am using the sanity + gatsby starter, and at the moment, the web deployment is not going through because it says that Gatsby needs a version of node higher than 18, and it says currently its using 16... But checking on both folders on my terminals and its confirming that im currently using node 18.12.1 ... so not sure whats going on. Thanks so much for your help.
can you show your setup please?
Would that be the package.json?
{ "private": true,
"name": "blog-with-gatsby-web",
"engines": { "node": ">=18.0.0"
},
"author": "Sanity <<mailto:hello@sanity.io|hello@sanity.io>>","scripts": { "build": "gatsby build",
"clean-cache": "gatsby clean",
"dev": "gatsby develop",
"format": "prettier-eslint --write \"**/*.js\" \"!.cache/**\" \"!node_modules/**\" \"!public/**\"","test": "echo \"Write tests! -> <https://gatsby.app/unit-testing>\""},
"devDependencies": { "autoprefixer": "^10.4.13",
"dotenv": "^16.0.0",
"gatsby-plugin-postcss": "^5.25.0",
"lint-staged": "^12.3.5",
"postcss": "^8.4.20",
"postcss-preset-env": "^7.3.1",
"prettier": "2.5.1",
"tailwindcss": "^3.2.4"
},
"dependencies": { "@babel/eslint-parser": "^7.19.1",
"@portabletext/react": "^1.0.1",
"@sanity/image-url": "^1.0.1",
"date-fns": "^2.28.0",
"fix": "^0.0.6",
"gatsby": "^5.3.3",
"gatsby-plugin-image": "^3.3.2",
"gatsby-plugin-manifest": "^5.3.1",
"gatsby-plugin-react-helmet": "^5.6.0",
"gatsby-plugin-sharp": "^5.3.2",
"gatsby-source-filesystem": "^5.3.1",
"gatsby-source-sanity": "^7.3.2",
"gatsby-transformer-sharp": "^5.3.1",
"latest": "^0.2.0",
"npm5": "^5.0.0-beta.69",
"react": "^18.0.0",
"react-dom": "^18.0.0",
"react-helmet": "^6.1.0"
}
}
can you test the version of node by using
node -vin your terminal, please?
yes i have 18.12.1
You need to show us the error i think, your information is pretty thin at the moment 🙂
And in my deployment it tells me this:
and terminals tells me otherwise
:face_with_peeking_eye:
Well seems like you do not have node installed locally in the project i think… can you check the link please?
yes but you you can have different version of packages installed in projects… seems like you do here as well.
go into your project and check there as well i would recommend
😉And then you can follow this instruction (
https://www.gatsbyjs.com/docs/upgrading-node-js/ )
go into your project and check there as well i would recommend
😉And then you can follow this instruction (
https://www.gatsbyjs.com/docs/upgrading-node-js/ )
user J Thanks Saskia, I've checked on both folders and both indicate that the node version installed is 18.12.1. Would updating each package to the latest version solve the issue?
user J, sorry meant to say dependencies.. :face_with_peeking_eye:
I make EXACTLY the same mistake all the time… millivanilly interchanging lib, package, plugin or dependency or nodemodules whenever I am in my zone 😉BUT: language is not as strict in real life (even with computers) so, no need to feel weird (and I have studied neurolingustics, so you can trust me
🤓)
🤓)
I will look into this later this week, if no-one gets in here earlier.
(as in not today but tomorrow or the day after)
user J thats cool! Thank you so much!
user J I was able to solve it! I added a file to the root directory that indicated to Netlify which version of node should run whenever building the websites. Therefore solving the incoherence of node versions on development and building. Thanks for your help as well ! 🙋♀️
Was this answer helpful?
Sanity – Build the way you think, not the way your CMS thinks
Sanity is the developer-first content operating system that gives you complete control. Schema-as-code, GROQ queries, and real-time APIs mean no more workarounds or waiting for deployments. Free to start, scale as you grow.
