npmlock2nix.node_modules started failing to populate artifacts #140
Description
A bump of nixpkgs, most likely the bump of nodejs from 14.x to 16.x (4c60ee3da1e) started causing npmlock2nix.node_modules to fail to populate the sources specified in package-lock.json.
https://nodesource.com/blog/whats-new-in-npm-8 mentions there's a new lockfile format, and npm seems to do a "one-time fixup" of the old lockfile.
This fails in the sandbox, as it obviously can't write back to that file.
If I invoke a npm install outside of the sandbox, it mentions fetching more metadata:
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
With the updated npm-lock.json, I then run the build again, and it fails to discover the provided tarballs:
last 10 log lines:
> patching sources
> configuring
> no configure script, doing nothing
> building
> npm ERR! code ENOTCACHEDmsill reify mark deleted [no
> npm ERR! request to https://registry.npmjs.org/zwitch/-/zwitch-1.0.5.tgz failed: cache mode is 'only-if-cached' but no cached response is available.
>
> npm ERR! A complete log of this run can be found in:
> npm ERR! /build/.npm/_logs/2022-01-25T10_17_37_004Z-debug.log
>
As of now, I was able to workaround this by passing nodejs = nodejs-14_x; in the call to npmlock2nix.node_modules.