Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/local/lib/node_modules/node-gyp/node_modules/env-paths/index.js from /usr/local/lib/node_modules/node-gyp/bin/node-gyp.js not supported.

[sam17896]

So our builds start seeing the following error few minutes ago, our last build was successful 2 hours ago. I notice a new version of the package is just published which may caused the issue.

Complete Error Message

npm ERR! Node.js v20.8.1
npm ERR! 
npm ERR! }
npm ERR!   code: 'ERR_REQUIRE_ESM'
npm ERR!     at Object.<anonymous> (/usr/local/lib/node_modules/node-gyp/bin/node-gyp.js:7:31) {
npm ERR! Instead change the require of index.js in /usr/local/lib/node_modules/node-gyp/bin/node-gyp.js to a dynamic import() which is available in all CommonJS modules.
npm ERR! Error [ERR_REQUIRE_ESM]: require() of ES Module /usr/local/lib/node_modules/node-gyp/node_modules/env-paths/index.js from /usr/local/lib/node_modules/node-gyp/bin/node-gyp.js not supported.
npm ERR! 
npm ERR!                               ^
npm ERR! const { default: envPaths } = require('env-paths')
npm ERR! /usr/local/lib/node_modules/node-gyp/bin/node-gyp.js:7
npm ERR! command sh -c node-gyp-build
npm ERR! command failed
npm ERR! path /usr/local/lib/node_modules/bcrypt
npm ERR! code 1
 ---> Running in 5e0ce068602f
Step 5/42 : RUN npm --build-from-source install -g bcrypt --unsafe-perm

[Dengjiansheng]

This version of env-paths has been upgraded to 3.0.0, and the require statement is now reporting an error.

I resolved this by specifying the node-gyp version:
yarn add -D node-gyp@11.5.0

[lukekarrys]

@sam17896 how is your version of node-gyp being set? this was released as a new major version because it dropped support for Node 18 (and some early versions of Node 20)

[lukekarrys]

Even though the change was included in a major release, I think it should be reverted. require(esm) landed in 20.19.0 but the engines of the latest major version includes ^20.17.0 meaning we support versions without require(esm).

[sebastianthomas94]

Confirming this issue affects Node.js 20.18.1-alpine in CI/CD environments (GitHub Actions and Coolify). The error occurs when compiling native modules like canvas@3.1.2 and @sentry/profiling-node.

Pinning to node-gyp@11 resolves the issue in Alpine-based Docker builds:

RUN npm install -g node-gyp@11

[itsanolive]

Confirming this has broken all of our github actions npm install step on Node 20.18.0

[lukekarrys]

Confirming this has broken all of our github actions npm install step on Node 20.18.0

@itsanolive @sebastianthomas94 @sam17896 can any/all of you run npm ls node-gyp in your project? i'm trying to see what dependency is pulling in the latest major version

(this change will be reverted anyway but it would be helpful to know the path that brings in node-gyp in projects)

[itsanolive]

Confirming this has broken all of our github actions npm install step on Node 20.18.0

@itsanolive @sebastianthomas94 @sam17896 can any/all of you run npm ls node-gyp in your project? i'm trying to see what dependency is pulling in the latest major version

(this change will be reverted anyway but it would be helpful to know the path that brings in node-gyp in projects)

We were using stmux for a dev process so that had a node-pty dependency, which referenced node-gyp. I'm moving us away from that stmux dependency anyway now, so it won't be an issue.