Repository navigation
aube add rewrites every existing package-lock.json entry and truncates funding arrays
#1810
This splits out the remaining parts of #1774, where you noted that the field reordering and NPM_BIN=/path/to/real/npm ./repro.sh
|
Replies: 3 comments
|
Thanks for the detailed repro. #1814 fixes this: existing One remaining gap: a newly resolved package with funding is still written as AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable. |
|
Implemented in #1814: fix(lockfile): preserve package-lock.json entry key order and funding |
|
Retested with
NPM_BIN=/path/to/real/npm ./repro.shIt now exits 0 with native npm 11.6.2 as the control. Fix shipped in aube 2.8.2 via #1814. Marking your reply as the answer. |
Thanks for the detailed repro. #1814 fixes this: existing
package-lock.jsonentries now keep npm's key order (so"dev": truestays put) and their fullfunding(type and arrays), and a read → write round trip of an npm-written lockfile is byte-identical.One remaining gap: a newly resolved package with funding is still written as
{"url": ...}, because the resolver only carries the URL. Existing entries are unaffected.AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable.