Multiple node-gyp errors when starting a new solid-start project - seems to be related to node_modules/@parcel/watcher

[componentscience]

Multiple node-gyp errors when starting a new solid-start project - seems to be related to node_modules/@parcel/watcher

[lxsmnsyc]

why was there a Parcel

[componentscience]

@lxsmnsyc @parcel/watcher was referenced based on the error output. I edited the title to hopefully make it more intuitive.

[darrenswhite]

adding this into package.json worked for me:

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

[ryansolid]

Hmm it looks like @vinxi/[email protected] uses @parcel/watcher. That being said if a version issue is happening that is upstream. I haven't seen this issue and I don't imagine it is related to our package locks. It looks like the current version we install for @parcel/watcher is 2.4.0

Looking further I see certain combinations seem to be having some issues with npm/node versions. parcel-bundler/watcher#156

I don't think there is much for us to do here. If Vinxi needs to reconsider libraries I suppose we could look that but it seems that there are some challenges with this package.

[devongovett]

Please try @parcel/watcher v2.4.1, which should fix this issue with npm 10.4.0. See parcel-bundler/watcher#156 (comment) for details.

[nksaraf]

Closing in favor or @devongovett's comment (#1310 (comment)). If its still an issue, reopen this.