Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@
},
"dependencies": {
"@isaacs/string-locale-compare": "^1.1.0",
"@npmcli/arborist": "^7.2.1",
"@npmcli/arborist": "^9.1.5",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep Arborist within npm's supported Node range

This upgrade makes a core dependency incompatible with the Node versions npm still advertises (^18.17.0 || >=20.5.0 in this same package.json). The published Arborist 9.x packages in this range declare engines.node as ^20.17.0 || >=22.9.0, so installs with engine-strict=true fail on supported Node 18.x/20.5–20.16, and the main install/audit/ls paths load @npmcli/arborist directly. Either keep this on a Node-18-compatible Arborist line or raise npm's own engine range with the major-version change.

Useful? React with 👍 / 👎.

"@npmcli/config": "^8.0.2",
"@npmcli/fs": "^3.1.0",
"@npmcli/map-workspaces": "^3.0.4",
Expand All @@ -78,12 +78,12 @@
"is-cidr": "^5.0.3",
"json-parse-even-better-errors": "^3.0.1",
"libnpmaccess": "^10.0.2",
"libnpmdiff": "^8.0.8",
"libnpmexec": "^10.1.7",
"libnpmfund": "^5.0.1",
"libnpmdiff": "^8.0.0",
"libnpmexec": "^10.0.0",
"libnpmfund": "^7.0.0",
"libnpmhook": "^11.0.0",
"libnpmorg": "^8.0.1",
"libnpmpack": "^9.0.8",
"libnpmpack": "^9.0.0",
"libnpmpublish": "^11.1.1",
"libnpmsearch": "^9.0.1",
"libnpmteam": "^8.0.2",
Expand Down