Getting Netlify deploy failures due to Node.js version?

Node.js v16.x entered Long Term Support (LTS) on October 27th. For some deployment configurations, this might have caused your Netlify Build to fail. Here’s what might be going on.

How it works

1. Check your Node.js engine version in ./package.json Example:

...
  "engines": {
    "node": ">=14.x",
    "yarn": ">=1.15"
  },
...

2. Then check your .nvmrc file Example:

lts/*

Does your project have similar settings? If so, this will fail the Netlify build. Here’s why:

• Node.js engines are restricted to v14.x only
• Netlify uses .nvmrc to set the Build container Node.js version. In this case it’s LTS, which is now Node.js 16.x

The Build container is using a Node.js version that your package.json does not allow.

How to set your config

There are a few things you can do to fix this configuration conflict.

Upgrade to Redwood v0.38

Redwood v0.38 is compatible with Node.js v16.x.

• Read the Release Notes and Upgrade

Change your .nvmrc

For the example above, you would want to set the .nvmrc file to use Node.js v14. Update .nvmrc:

- lts/*
+ v14

Final Steps

To apply the changes, you’ll most likely need to Trigger a Deploy with the cache cleared.

[jtoar]

Netlify deploy has been quite stable since v1. Closing mainly due to staleness, and that things are so different now it’d be hard to diagnose whatever the original problem was.

Note that we could definitely still reduce the size of functions… see https://github.com/redwoodjs/redwood/issues/5160

[thedavidprice]

@doesnotexist any updates here or still stuck on function size blowing up? These things can be tough to diagnose and, frankly, we’ve been struggling with Netlify’s build the past few releases. My guess is you’ll be just fine deploying if you make the switch to Vercel.

Please keep me posted.