watcher: gyp: binding.gyp not found (...) while trying to load binding.gyp

Solution temp

package.json

"overrides": {
    "@parcel/watcher": "2.1.0"
}

I tried some more combinations of Node and npm:

Same here. My workaround:

  "overrides": {
    "@parcel/watcher": "~2.1.0"
  }

I tried some more combinations of Node and npm:

Node 18.19.0 Node 20.11.0 npm v10.2.3 ✔️ ✔️ npm v10.2.4 ✔️ ✔️ npm v10.2.5 ✔️ ✔️ npm v10.3.0 ✔️ ✔️ npm v10.4.0 ❌ ❌

Confirming the downgrade to npm v10.3.0 fixed the issue for me while using Node v20.11.0

Was on npm v10.4.0 and trying to set up Analog.js using npm install @analogjs/platform --save-dev and ran into this error:

npm ERR! code 1
npm ERR! path /Users/<redacted>/Projects/<redacted>/website/node_modules/@parcel/watcher
npm ERR! command failed
npm ERR! command sh -c node-gyp rebuild
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@10.0.1
npm ERR! gyp info using node@20.11.0 | darwin | x64
npm ERR! gyp info find Python using Python version 3.7.3 found at "/Library/Developer/CommandLineTools/usr/bin/python3"

After downgrading, the install completed successfully.

I tried some more combinations of Node and npm: Node 18.19.0 Node 20.11.0 npm v10.2.3 ✔️ ✔️ npm v10.2.4 ✔️ ✔️ npm v10.2.5 ✔️ ✔️ npm v10.3.0 ✔️ ✔️ npm v10.4.0 ❌ ❌

As found out by vincesp, downgrading npm to v10.3.0 on Node 18.17.1 did help! I ran npm install -g npm@10.3.0 for the downgrade just fyi.

Thanks!

I have the same exact error when installing Nuxt.

In my case @parcel/watcher is a direct dependency of another package. Solved by fixing version on that dependency:

"overrides": { "package-that-uses-parcel": { "@parcel/watcher": "2.1.0" } }

Great info @lovell! Thanks so much for sharing. It’s interesting because this seems to have been happening even before npm 10.4 Perhaps that’s actually a different issue (with lockfiles?) though.

I updated our publishing workflow to copy the files needed into a separate directory and run npm publish from there. That way binding.gyp doesn’t get added by npm (even though it already wasn’t included in package.json files).

In a related change, I also added better error handling to the package so that if an error occurs while requiring the native module, we only continue trying fallback locations if the error was a module not found error. Other errors (e.g. incompatibilities with OS versions) are re-thrown so they are reported to users.

These changes are published in v2.4.1. I tested locally with npm 10.4.0 and was able to install the package successfully. Please let me know if you continue to run into issues.

“@parcel/watcher”: “2.1.0”

First time trying Nuxt today, and I get this 😦

Can confirm that this causes fresh nuxt installations to fail when using npx nuxi init. Quite annoying for people that are new to the framework since they won’t know they have to override the package.json to fix it

I have the same exact error when installing Nuxt.

+1 Updated package.lock in nuxt 3 and thought it’s the infamous npm cache permissions bug. But even after chowning and reinstalling node, the error stayed. Turns out it was due to this package.

Tested overrides with all sorts of in-between versions. The first version to work is 2.1.0

Env: Node 21.6 OS macOS Sonoma Arch arm64 (M1 Pro)

@devongovett PR https://github.com/parcel-bundler/watcher/pull/144 removed the install script from package.json as part of v2.2.0 however the npm registry still reports an install script:

$ npm show @parcel/watcher@2.1.0 --json | grep install
    "install": "node-gyp-build",
$ npm show @parcel/watcher@2.2.0 --json | grep install
    "install": "node-gyp rebuild"
$ npm show @parcel/watcher@latest --json | grep install
    "install": "node-gyp rebuild"

I think this erroneous install script is being injected at npm publish time because npm sees a binding.gyp file (thanks to the logic in @npmcli/node-gyp), however this file isn’t published.

A few possible solutions, from hardest to easiest:

• Fix @npmcli/node-gyp so it checks to see if binding.gyp will actually be published (e.g. look in files or .npmignore).
• Move all the src and related build files, including binding.gyp, out of the root directory of this repo so it no longer looks like a native module (I did this for sharp, it works a treat, removes a whole class of error in most Electron tooling as well).
• Remove the binding.gyp file from the filesystem just before running npm publish.

npm v10.4.0 introduced https://github.com/npm/run-script/pull/192 which completely changes the way that package.json files are parsed at npm install time and is likely to have exposed this issue.

Can reproduce this with ‘npm install’ in a SolidJS project.

$ node –version v20.11.0 $ node-gyp –version v10.0.1 $ npm –version 10.4.0 $ uname -a Linux 6.7.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 01 Feb 2024 10:30:35 +0000 x86_64 GNU/Linux

[host@myhost site]$ npm install npm ERR! code 1 npm ERR! path /home/host/site/node_modules/@parcel/watcher npm ERR! command failed npm ERR! command sh -c node-gyp rebuild npm ERR! gyp info it worked if it ends with ok npm ERR! gyp info using node-gyp@10.0.1 npm ERR! gyp info using node@20.11.0 | linux | x64 npm ERR! gyp info find Python using Python version 3.11.6 found at “/sbin/python3” npm ERR! gyp info spawn /sbin/python3 npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args ‘/home/host/.nvm/versions/node/v20.11.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py’, npm ERR! gyp info spawn args ‘binding.gyp’, npm ERR! gyp info spawn args ‘-f’, npm ERR! gyp info spawn args ‘make’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘/home/host/site/node_modules/@parcel/watcher/build/config.gypi’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘/home/host/.nvm/versions/node/v20.11.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘/home/host/.cache/node-gyp/20.11.0/include/node/common.gypi’, npm ERR! gyp info spawn args ‘-Dlibrary=shared_library’, npm ERR! gyp info spawn args ‘-Dvisibility=default’, npm ERR! gyp info spawn args ‘-Dnode_root_dir=/home/host/.cache/node-gyp/20.11.0’, npm ERR! gyp info spawn args ‘-Dnode_gyp_dir=/home/host/.nvm/versions/node/v20.11.0/lib/node_modules/npm/node_modules/node-gyp’, npm ERR! gyp info spawn args ‘-Dnode_lib_file=/home/host/.cache/node-gyp/20.11.0/<(target_arch)/node.lib’, npm ERR! gyp info spawn args ‘-Dmodule_root_dir=/home/host/site/node_modules/@parcel/watcher’, npm ERR! gyp info spawn args ‘-Dnode_engine=v8’, npm ERR! gyp info spawn args ‘–depth=.’, npm ERR! gyp info spawn args ‘–no-parallel’, npm ERR! gyp info spawn args ‘–generator-output’, npm ERR! gyp info spawn args ‘build’, npm ERR! gyp info spawn args ‘-Goutput_dir=.’ npm ERR! gyp info spawn args ] npm ERR! gyp: binding.gyp not found (cwd: /home/host/site/node_modules/@parcel/watcher) while trying to load binding.gyp npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: gyp failed with exit code: 1 npm ERR! gyp ERR! stack at ChildProcess.<anonymous> (/home/host/.nvm/versions/node/v20.11.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:271:18) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:518:28) npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:294:12) npm ERR! gyp ERR! System Linux 6.7.3-arch1-1 npm ERR! gyp ERR! command “/home/host/.nvm/versions/node/v20.11.0/bin/node” “/home/host/.nvm/versions/node/v20.11.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild” npm ERR! gyp ERR! cwd /home/host/site/node_modules/@parcel/watcher npm ERR! gyp ERR! node -v v20.11.0 npm ERR! gyp ERR! node-gyp -v v10.0.1 npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/host/.npm/_logs/2024-02-05T14_27_16_860Z-debug-0.log

Having the same issue since at least Aug 16: node: v18.17.1 npm: v9.6.7 Tried downgrading to node 16.15 (npm 8.11), same error. Also tried forcing @parcel/watcher version to 2.1 and 2.3.