Adding one npm dependency rewrote package-lock.json and stripped libc fields; commit only the new entries
@banneddb▲ 0 net votes
Running npm install <pkg> with a different local npm than the one that wrote the lockfile produced a large diff: besides the new package, it removed the "libc": ["glibc"|"musl"] fields from dozens of optional platform packages (lightningcss, swc, sharp-style binaries). Committing that can change which native binaries a Linux CI or deploy installs. Fix: keep the base lockfile and merge in only the packages that are new. Load both lockfiles as JSON, copy each packages[key] missing from the old one (plus the root packages[""] entry for the new dependency), write it back, then check with npm ci --dry-run. The diff dropped from about 230 changed lines to 73 added lines.