v2.2.0 node-gyp rebuild error, incorrect scripts in npm registry about watcher HOT 11 OPEN

Same error on Windows 10
node: 18.17.1
npm: 9.8.1
node_gyp: 9.4.0

npm i @parcel/[email protected] installs just fine.
npm i @parcel/[email protected] --ignore-scripts works too but that's not the way to go.

I'm adding "@parcel/watcher": "~2.1" to my dependencies until this is fixed.

from watcher.

I don't understand why the npm registry would have that extra script. It doesn't not appear in the package.json

It's right there, named build (originally rebuild (834994b), before you renamed it with v2.2.0-alpha.0).

Correct me if I'm wrong but I see two issues that were introduced in 062bca4:

• prebuilds are no longer used because the prebuilds dir created by prebuildify isn't packaged anymore and the recommended "install": "node-gyp-build" script was removed. Instead, there's now a build script that tries to run node-gyp rebuild when the package is installed.
• node-gyp rebuild fails because src and bindings.gyp were removed from the package files as well

from watcher.

I don't understand why the npm registry would have that extra script. It doesn't not appear in the package.json https://unpkg.com/browse/@parcel/[email protected]/package.json

from watcher.

Any news on this?

from watcher.

I'm also having the same issue, is there any progress, please

from watcher.

Issue persists in v2.3.0 btw.

from watcher.

Issue persists in v2.3.0 btw.

unfortunately, I feel like they're not going to fix this

from watcher.

I had to use "@parcel/watcher": "~2.1.0" in my project devDependencies to avoid problems with 'gyp: binding.gyp not found' on both Windows 10 with Python 3.11 and MacOS 12.6.5 with Python 3.10. The problems seem to start in "@parcel/watcher": "~2.2.0" with its "node-addon-api": "^7.0.0" dependency.

from watcher.

npm install --save-dev parcel, as described in the docs, fails in a clean project directory. How is this not getting more attention?

from watcher.

@DustInComp Which OS, Node and npm version are you using?

from watcher.

Which OS, Node and npm version are you using?

@mischnic Windows 10 Pro 19045.3693, Node 20.9.0, npm 10.2.4

Actually, I seem to have just resolved the issue on my end by updating our private package registry/proxy from Verdaccio version 5.14.0 to 5.27.0. However, I'm not sure how this update actually fixed the problem. The only change in installation I can find is the modules' "resolved" file paths in the package-lock.json.
Before: https://<verdaccio>/@parcel%2fwatcher/-/watcher-2.3.0.tgz
After: https://<verdaccio>/@parcel/watcher/-/watcher-2.3.0.tgz

Maybe other users who've had this issue had a similar setup?

from watcher.