[BUG] sh -c node-gyp rebuild fails

[jamesmurdza]

What happened?

Hi! Plasmo works fine on my system. Unfortunately I've tried showing two people how to use it and they both ran into dependency errors with node-gyp when trying to build new Plasmo apps.

This happens on npm run dev. Is this a common issue? It seems like a node-gyp issue, but many are running into it.

Here's a stream where we tried to debug it: https://youtu.be/4lbnB2f_Z5M?t=1035

Version

Latest

What OS are you seeing the problem on?

Windows, MacOSX

What browsers are you seeing the problem on?

No response

Relevant log output

No response

(OPTIONAL) Contribution

• I would like to fix this BUG via a PR

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems.

[tommyle]

Try installing node-gyp globally

yarn global add node-gyp

[jamesmurdza]

Hi! Thanks for the reply.

If you have a look at the screenshot and stream link above: The command that failed was installing node-gyp globally. I don't think it should make a difference if npm or yarn is used?

[dougwithseismic]

Also experiencing this via npm - using pnpm works fine, at least here.
General consensus seems to point towards some BS with @parcel/watcher and npm compatibility 🤷‍♀️.

parcel-bundler/watcher#156

[PythonCoderAS]

The latest version of @parcel/watcher seems to fix this. Can you update the underlying version to use 2.4.1? Seems that one of the dependencies has locked @parcel/watcher to a specific version