Currently the continuous build is giving WARN EBADENGINE warnings at the npm install stage, complaining that various Angular packages require a newer npm version.
The build image is based on Debian testing, which currently has npm 7.5.2, but these packages apparently require at least 7.5.6.
This doesn't seem to be actively breaking anything, so it's probably OK to just wait for Debian testing to get at least this npm version, then build a new base image.
The package-lock.json file was generated using npm 7.5.2, so we should maybe consider recreating that using a newer version as well, when available.
I tried recreating package-lock.json, but I got some resolution errors stemming from indirect dependencies of firebase. I'll take a look at these separately.
Currently the continuous build is giving
WARN EBADENGINE
warnings at thenpm install
stage, complaining that various Angular packages require a newernpm
version.The build image is based on Debian
testing
, which currently hasnpm
7.5.2, but these packages apparently require at least 7.5.6.https://packages.debian.org/bullseye/npm
This doesn't seem to be actively breaking anything, so it's probably OK to just wait for Debian
testing
to get at least thisnpm
version, then build a new base image.The
package-lock.json
file was generated usingnpm
7.5.2, so we should maybe consider recreating that using a newer version as well, when available.