`EBADPLATFORM` from `npm ci` when running on netlify with >= `12.2.9`

[tjenkinson]

Describe the bug

npm ci on netlify fails with

7:41:18 PM: npm ERR! code EBADPLATFORM
7:41:18 PM: npm ERR! notsup Unsupported platform for @esbuild/android-arm@0.15.15: wanted {"os":"android","arch":"arm"} (current: {"os":"linux","arch":"x64"})
7:41:18 PM: npm ERR! notsup Valid OS:    android
7:41:18 PM: npm ERR! notsup Valid Arch:  arm
7:41:18 PM: npm ERR! notsup Actual OS:   linux
7:41:18 PM: npm ERR! notsup Actual Arch: x64
7:41:18 PM: npm ERR! A complete log of this run can be found in:
7:41:18 PM: npm ERR!     /opt/buildhome/.npm/_logs/2022-12-18T19_41_17_238Z-debug-0.log

See build run here

Steps to reproduce

View this test repo.

It does not contain a package-lock, meaning the first npm i generates a package-lock on the instance. It then does an npm ci, which fails with the error above.

This did not used to happen with versions <= 12.2.8.

Ref video-dev/hls.js#5114
Ref video-dev/hls.js#5115

Configuration

https://github.com/tjenkinson/netlify-cli-install-error/blob/main/netlify.toml

Environment

My local environment shouldn't be relevant for this. Please see the repro.

[danez]

This is actually a problem in npm see npm/npm#2679 and evanw/esbuild#1707

I will try to manually patch our shrinkwrap to exclude these packages that were introduced in 26c409d#diff-44a7c69871c5958e657226d5552c9451606a778233fb824f68530d0cfd3f8994

[tjenkinson]

Interesting maybe we can switch to a newer npm on netlify then to workaround it

[tjenkinson]

Although we are on the most recent lts (18.12.1) so it would be great if it could work again with that

[tjenkinson]

Any fix planned for this? We are now getting prompted to upgrade to fix a security issue

thanks

[danez]

Unfortunately, we cannot fix this from our side at the moment yet. npm seems to have a lot of issues with shrinkwrapping, and all attempts to fix this so far just created more problems.

[tjenkinson]

Ok thanks for trying.

I wrote a small cli to workaround the issue. https://github.com/tjenkinson/npm-ci-please

So we can use npx -y npm-ci-please@1 in place of npm ci and it should just work™️

Hopefully at some point npm will actually fix the root of the problem 🤞