I’ve been using netlify dev locally for some time, but after updating to Node v24.0.0, running netlify dev now gives me:
› TypeError: Cannot read properties of undefined (reading 'prototype')
Any ideas?
I’ve been using netlify dev locally for some time, but after updating to Node v24.0.0, running netlify dev now gives me:
› TypeError: Cannot read properties of undefined (reading 'prototype')
Any ideas?
CLI is expected to work only with Node LTS. Have you tried with Node 22?
Yep, I had switched to 24 yesterday. So it should not work with the “Current” version, only LTS?
We don’t test it on current. It might work, or it might not. It’s an industry standard practice to ensure compatibility with the LTS versions. Some major versions of Node don’t affect the CLI, while others might. We can’t keep chasing every new version they release, so we stick to LTS.
@hrishikesh
Does that go the same for the Netlify platform itself? Would it be safe to assume once Node 24 becomes LTS at the end of October, Netlify would then start to support it?
Netlify Builds already support Node 24. AWS does not. So your build Node.js version would not match your Function execution version, which sometimes causes issues.
Can confirm same error on Arch Linux when upgraded to nodejs (25.1.0-3), and had to downgrade back to nodejs-lts-jod (version 22.x).
v24 is now the active LTS. In out Netlify deploys Dependency Management configuration, the highest selectable node version is 22.x. Can you help clarify how to configure builds to support Node 24?
@hrishikesh
AWS now lists Node 24 support
And Vercel has also confirmed support
Do we have an ETA for Netlify support?
Builds can already using any version of Node regardless of the option available in the UI: Manage build dependencies | Netlify Docs. As for Functions, we don’t have any timelines on when Node 24 would be available to select in the UI. I think you can set AWS_LAMBDA_JS_RUNTIME environment variable with the value nodejs24.x till then.