Problem with fsevents@1.2.7 and Node.js 12

Since the Node.js 12 update I’ve been unable to install GOV.UK Frontend via npm ci (clean install from lockfile) without errors:

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for fsevents@1.2.7 and node@12.13.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Pre-built binaries not installable for fsevents@1.2.7 and node@12.13.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)

npm WARN deprecated fsevents@1.2.9: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size

No pre-built binary exists for fsevents@1.2.7 on Node.js 12 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz

The current lockfile in the project requires fsevents@1.2.7 for Gulp, Jest and Nodemon.

Version 1.2.9+ is required for Node.js 12 compatibility.

[colinrotherham]

@nickcolley Can I fix that please??

I always got it twice when developing with GOV.UK Frontend! 😁

But now we’re returning a promise from “gulp watch” you’ve got another condition where files are changed after the nodemon/watchers have started.

i.e. Nodemon has received two file change events, so you see the initial startup log plus two more restarts in the terminal (3 in total).

[colinrotherham]

If you want a clean install exactly as the author intended use npm ci (removes node_modules and installs the exact versions found in the lockfile).

If you want minor version bumps and patch releases to be included use npm install, best avoided as this can slip in unintended consequences to production.