Migrate from npm CLI to pnpm#1211
Merged
saulecabrera merged 2 commits intoMay 21, 2026
Merged
Conversation
Improve supply-chain security for the javy npm package by switching its install/build/publish flow to pnpm. pnpm refuses to execute install scripts from transitive dependencies by default, uses a content-addressed store that detects tampered tarballs, and enforces strict dependency isolation. Pins pnpm 10.28.0 via the packageManager field so local dev and CI run the same version. Replaces package-lock.json with pnpm-lock.yaml. CI workflows install pnpm via pnpm/action-setup, pointed at npm/javy's package.json for the version. Tracks bytecodealliance#1210.
Apply the same supply-chain hardening to the Web Platform Tests harness so contributors and CI don't need the npm CLI to run WPT. Updates the Makefile test-wpt-ci target and the WPT step in ci.yml to use pnpm, switches the inner test script to pnpm run, and pins pnpm 10.28.0 via the packageManager field. Tracks bytecodealliance#1210.
saga-dasgupta
force-pushed
the
sd.pnpm_migration
branch
from
3f8f77d to
b713485
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
javynpm package and the WPT harness from thenpmCLI topnpm, replacing bothpackage-lock.jsonfiles withpnpm-lock.yaml.pnpm@10.28.0via thepackageManagerfield so local dev and CI use the same version, and addpnpm/action-setup@v4to the three workflows that touched npm.Makefiletest-wpt-citarget and contributor READMEs to usepnpminvocations.The package continues to publish to the npm registry as
javy; only the CLI used to install and run scripts changes. Dependabot'spackage-ecosystem: npmentry stays — it readspnpm-lock.yamlnatively.Motivation
Improve supply-chain security for Javy's JS tooling.
pnpmmitigates several classes of npm supply-chain risk: it refuses to execute install scripts from transitive dependencies by default, uses a content-addressed store that detects tampered tarballs across projects, and enforces strict dependency isolation so packages can only resolve what they explicitly declared. PinningpackageManagermakes the toolchain version part of the lockfile contract so contributors and CI all run the samepnpm.Tracks #1210.