Explain npm error code

What this npm error sample shows

code, path and command

npm error code 1 comes with command failed: the dependency's install command exited with an error, and npm itself then exited with code 1. It isn't make's code, which was 2. path and command say where and what: the install step of native-thing inside node_modules, sh -c node-gyp rebuild. So the failure is in a dependency's build, not in your own files.

the line with the cause

Most of the block is node-gyp reporting on itself. The cause is the make: *** No rule to make target line: make had no way to build addon.o because src/addon.cc, the addon's source file, isn't there. gyp ERR! build error and the make exit code 2 after it report that same failure.

code 127 and ENOENT

npm run build with vite not installed printed sh: line 1: vite: command not found and exited with code 127, the shell's code for a command it can't find. npm --prefix web run dev with no web folder printed npm error code ENOENT and Could not read package.json, and exited with code 254.

the debug log

The last line names a debug log in ~/.npm/_logs, a new one for each run. This one had 96 lines, including error code 1 and verbose exit 1. It's the file to attach when you ask for help, after checking it for anything private.

Good to know

• Run with npm 11.10.1 and Node.js 25.7.0 on Linux, in a test project. native-thing is a local test package whose install script runs node-gyp on a binding.gyp that lists a missing src/addon.cc. It was installed with npm install --install-links, so the local package was copied into node_modules the way a registry package is; the sample shows the command as npm install. Paths are shortened to ~, and node-gyp used the headers from the local Node.js install, so nothing was downloaded.
• When a script itself fails, npm 11.10.1 adds no npm error lines: npm run dev with server.js throwing Error: ENOENT: no such file or directory, open './config.json' printed npm's > node server.js header, then only the Node.js error, and exited with code 1. A script that doesn't exist gives npm error Missing script: "test".
• npm uninstall native-thing and a config.json fixed both: npm run dev then printed listening on 3000.

Watch out: The last lines aren't the cause. Here they are gyp ERR! not ok and the log path, while the line that names the problem, No rule to make target 'Release/obj.target/addon/src/addon.o', is line 40 of the 52 lines in the full output, after 28 lines of node-gyp detail and a 2-line Node.js deprecation warning. Search for that line, the first error from the tool that failed, not for the last line.