Investigate `npm ci` issues on azure

Case 1:

This is the common reason why npm ci fails. This is apparently caused by bundled dependencies inside some packages.

10878 verbose stack Error: ENOENT: no such file or directory, open 'd:\a\1\s\node_modules\chokidar\node_modules\fsevents\node_modules\node-pre-gyp\package.json'
10879 verbose cwd d:\a\1\s
10880 verbose Windows_NT 10.0.14393
10881 verbose argv "C:\\hostedtoolcache\\windows\\node\\10.11.0\\x64\\node.exe" "C:\\npm\\prefix\\node_modules\\npm\\bin\\npm-cli.js" "ci"
10882 verbose node v10.11.0
10883 verbose npm  v6.10.3
10884 error code ENOENT
10885 error syscall open
10886 error path d:\a\1\s\node_modules\chokidar\node_modules\fsevents\node_modules\node-pre-gyp\package.json
10887 error errno -4058
10888 error enoent ENOENT: no such file or directory, open 'd:\a\1\s\node_modules\chokidar\node_modules\fsevents\node_modules\node-pre-gyp\package.json'
10889 error enoent This is related to npm not being able to find a file.

[hmottestad]

FYI. I’m seeing this with GitHub actions today too. So by no means fixed. Found this thread while googling. Good to know I’m not alone 😃

[luabud]

Closing as stale.