Build Error: No prebuild or local build of @parcel/watcher found.

[patreilly]

Environment information

System:
  OS: macOS 14.5
  CPU: (8) arm64 Apple M1
  Memory: 193.45 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 22.3.0 - /opt/homebrew/bin/node
  Yarn: undefined - undefined
  npm: 10.8.1 - /opt/homebrew/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 1.0.3
  @aws-amplify/backend-cli: 1.0.3
  aws-amplify: 6.3.5
  aws-cdk: 2.143.1
  aws-cdk-lib: 2.143.1
  typescript: 5.4.5
AWS environment variables:
  AWS_PROFILE = retaildemo
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description

i'm getting this build error for a package I believe codebuild uses during the build process, but i have no control over how this is used during deployment:

Error: No prebuild or local build of @parcel/watcher found. Tried @parcel/watcher-linux-x64-glibc. Please ensure it is installed (don't use --no-optional when installing with npm). Otherwise it is possible we don't support your platform yet. If this is the case, please report an issue to https://github.com/parcel-bundler/watcher.

I've attempted the following to fix this:

• Updated the amplify.yml to remove --cache .npm --prefer-offline from npm ci call
• Ran npm cache clean --force , deleted the node_modules folder and did a fresh npm install
• deleting the package-lock.json and recreating

BUILD.txt

[josefaidt]

Hey @patreilly 👋 thanks for raising this! We chatted offline and found that in a clean install (i.e. no node_modules/ or package-lock.json) the lockfile contained entries for each platform's addon. However if the lockfile is deleted and regenerated while node_modules/ still exist, only the addon for your host system is declared in the lockfile. This causes issues where after installing dependencies in the build system with npm ci, the linux addon is not installed and thus the failure in amplify pipeline-deploy

I'll mark this as a dependency issue for tracking, but seems similar to parcel-bundler/watcher#152

As a workaround, delete both the lockfile and node_modules/, then reinstall with npm install

[patreilly]

This in fact fixed the issue.

[edwardfoyle]

This is actually an npm bug, not a parcel bug: npm/cli#4828
The workaround above is corroborated by this comment as well

[josefaidt]

Closing in favor of tracking the issue filed in the npm CLI's repo