Glitch Could not find node

Yesterday out of nowhere without changing a single line of code, my glitch started refusing my code that was running smoothly before.

now it displays

Could not find node 16.14.2, using 10

6:42 AM

node v10.24.1, npm 6.14.12

6:42 AM

Installing…

than it errors out because it is not running correct Node version.

I’ve tried

“engines”: {
“node”: “16.14.2”
},

“engines”: {
“node”: “>=16.14.2”
},

“engines”: {
“node”: “>=16.0.0”
},

“engines”: {
“node”: “16.X”
},

But none of the above worked. What can I do to fix my code?

Could I get you to write in to support@glitch.com with details on which project/username, so we can dig into what’s happening there?

Just did that. I’ll wait for an answer. Tks

@Pomax I’m still waiting for an answer. I did a rewind and fixed the project, but moments after, it rebooted and could not find node again… really weird thing going on.

{
“name”: “whatsapp-echo-webhook”,
“version”: “1.0.0”,
“description”: “”,
“main”: “server.js”,
“type”: “module”,
“scripts”: {
“start”: “node server.js”
},
“author”: “WhatsApp Team”,
“license”: “MIT”,
“dependencies”: {
“aws-sdk/client-s3”: “^3.685.0”,
“hapi/boom”: “^10.0.1”,
“supabase/supabase-js”: “^2.46.1”,
“whiskeysockets/baileys”: “^6.7.9”,
“axios”: “^1.7.7”,
“bcryptjs”: “^2.4.3”,
“cors”: “^2.8.5”,
“dotenv”: “^16.4.5”,
“express”: “^5.0.1”,
“jsonwebtoken”: “^9.0.2”,
“node-schedule”: “^2.1.1”,
“openai”: “^4.70.3”,
“p-limit”: “^6.1.0”,
“pg”: “^8.13.1”,
“pino”: “^9.5.0”,
“qrcode”: “^1.5.4”,
socket.io”: “^4.8.1”,
“socketio”: “^1.0.0”,
“sqlite3”: “^5.1.7”
},
“engines”: {
“node”: “16.14.2”
},
“keywords”:
}

When you open the log for your project (it’s a button in the bottom bar), is there anything indicative in there? Also, without knowing which project you’re working on: if it’s a public project, what’s the project url?

Hello, I have the same issue, will email support

I encountered exactly the same issue. Suddenly, my web app stopped working today. The logs show a message saying “Could not find node >=16.0.0, using 10,” which led to a syntax error.

Here’s the project:

(Update)
When I split the project in Remix, the server for the separated part started without any issues.

Yeah I cloned a git repo and glitch keeps insisting on using node version 10 because it can’t find >=18, any workarounds?

backport it to node 16 or you can try installing a newer node interpreter. I have a starter here with node 22 Node.js 22 starter but it takes extra time to start up because it has to set up node each time

@Pomax suddenly this started occurring again. Please I need support. Never got an answer back from the e-mail I sent.

There was some host cycling roughly the same time you wrote your message, so that might have been a red herring: does it work now? (if not, support should have reached out now)