Skip to content

Sync wasm32-wasi package lockfile dependency versions#20024

Open
mike-lmctl wants to merge 1 commit intotailwindlabs:mainfrom
mike-lmctl:fix-wasm-runtime-lockfile
Open

Sync wasm32-wasi package lockfile dependency versions#20024
mike-lmctl wants to merge 1 commit intotailwindlabs:mainfrom
mike-lmctl:fix-wasm-runtime-lockfile

Conversation

@mike-lmctl
Copy link
Copy Markdown

Fixes #20016

Summary

The @tailwindcss/oxide-wasm32-wasi package manifest already declares @napi-rs/wasm-runtime as ^1.1.4, along with the newer matching @emnapi/* dependencies, but its nested pnpm-lock.yaml still resolved the older 1.0.5 runtime and 1.5.0 @emnapi packages.

This regenerates the nested wasm32-wasi lockfile so the bundled dependency tree matches the package manifest.

Test plan

Ran these from crates/node/npm/wasm32-wasi:

pnpm install --lockfile-only --ignore-workspace --lockfile-dir .
pnpm install --ignore-workspace --frozen-lockfile --ignore-scripts

The frozen install reports the lockfile is up to date.

The wasm32-wasi package manifest already requires @napi-rs/wasm-runtime
^1.1.4 and matching @emnapi packages, but its nested pnpm lockfile still
resolved older 1.0.x/1.5.x packages. Regenerate that nested lockfile so the
bundled dependency tree matches the package manifest.

Tested: pnpm install --lockfile-only --ignore-workspace --lockfile-dir . (from crates/node/npm/wasm32-wasi)
Tested: pnpm install --ignore-workspace --frozen-lockfile --ignore-scripts (from crates/node/npm/wasm32-wasi)
@mike-lmctl mike-lmctl requested a review from a team as a code owner May 7, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dependency to @napi-rs/wasm-runtime leads to invalid dependency tree

1 participant