Why Did Dependency Installation Fail?

Occasionally, dependency installation may fail for your site with an error similar to the following:

09:14:56 AM: NPM ci --unsafe-perm --prefer-offline --no-audit failure - Command failed with exit code 1 (EPERM): npm ci --unsafe-perm --prefer-offline --no-audit --registry=https://registry.npmjs.org/

09:14:58 AM: NPM ci --unsafe-perm --prefer-offline --no-audit attempt 1 of 3...

09:15:02 AM: npm ERR! bindings not accessible from webpack-dev-server:fsevents

This is usually due to an out of sync lock file ^{1, 2}. In most cases, this can be resolved by doing the following:

1. On your local machine, delete all node_modules for your project
2. Delete package-lock.json or yarn.lock
3. Re-install dependencies
4. Commit the new lock file
5. Push the updated lock file to your remote repository

References

[1] https://classic.yarnpkg.com/en/docs/yarn-lock/

[2] https://docs.npmjs.com/cli/v7/configuring-npm/package-lock-json