@oxc-resolver/binding-*
This is a genuine quality improvement hiding inside a routine bump. In the old knip 6.27.0, the @oxc-parser/binding-wasm32-wasi entry pulled in @napi-rs/wasm-runtime 1.2.0, which had a hard peer dependency on @emnapi/core ^2.0.0-alpha.3 — meaning the alpha 2.0 emnapi was forced into the tree, along with its @emnapi/wasi-threads and extra tslib copies. The new @napi-rs/wasm-runtime 1.2.2 accepts ^1.7.1 || ^2.0.0-alpha.3, so the stable 1.11.x emnapi path works. The alpha 2.0 entries under knip/node_modules/ (lines 21379–21436, deleted) are the other half of this cleanup — they were the peer deps that satisfied the old constraint. The net effect: fewer dependencies, fewer WASI threads copies, and no alpha-version peer in the tree.
@oxc-parser/binding-wasm32-wasi
@napi-rs/wasm-runtime
@emnapi/core ^2.0.0-alpha.3
@emnapi/wasi-threads
tslib
^1.7.1 || ^2.0.0-alpha.3
knip/node_modules/
Cut in editing (praise)
The 'safe' label in the PR title is a compression of a risk assessment whose full reasoning lives in the PR description body. Has the team considered a structured mechanism — a label, a check-run, a required CI gate — to encode the safety determination so it's queryable across the dependency-update PR corpus? Right now 'safe' lives only in prose, which means the corpus of past determinations can't be mined to tune the cooldown or risk model.