[lukastaegert]

Rollup Plugin Name: wasm

This PR contains:

• bugfix
• feature
• refactor
• documentation
• other

Are tests included?

• yes (bugfixes and features will not be merged without tests)
• no

Breaking Changes?

• yes (breaking changes will not be merged unless absolutely necessary)
• no

List any relevant issue numbers:

• Similar to feat(json): add Rollup 5 compatibility #2017
• In feat(alias,auto-install,beep,buble,commonjs,data-uri,dsv,dynamic-import-vars,eslint,esm-shim,graphql,image,inject,legacy,multi-entry,node-resolve,pluginutils,replace,run,strip,sucrase,swc,terser,typescript,url,virtual,yaml): support rollup 5 #2037, I found that the wasm plugin, like the json plugin, needs some changes for Rollup 5, which is added here

Description

Rollup 5 makes import attributes part of module identity, so the id of an attributed import is the file path with an encoded ?attributes=... suffix. As the plugin matched ids with /\.wasm$/ and createFilter, attributed Wasm imports were never loaded or transformed, and Rollup tried to parse the binary as JavaScript.

The load and transform hooks now use the rawId option for the filter, the extension check, the watched file, the file operations and the key of the emitted asset map, falling back to the id for earlier Rollup versions that do not pass it. Keying assets by the raw id keeps a single emitted file when the same Wasm is imported with different attributes.

The target environment tests now run without tree-shaking since Rollup 5 removes the helper branches they assert on.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The behavior change is limited to the Wasm plugin and its Rollup 5 compatibility.

The plugin changes appear safe to merge, with a non-blocking build-environment mismatch to address.

Findings

1.  Build tool outgrows Node 20 ▶

_{Reviews (1) · Last reviewed commit: "feat(wasm): support rollup 5" · Reviewed by Greptile}

[greptile-apps]

Build tool outgrows Node 20

Both CI matrices and .nvmrc still select Node 20, but catalog:rollup-next selects Rollup 5, which requires Node 22.22.0 or newer. The package's build script runs that Rollup directly, putting local builds and the Node 20 CI jobs outside its supported environment. Update the build environment alongside this dependency, or keep a supported build tool for Node 20.

[Copilot]

🟡 Changes recommended

Rollup 5.0.0-2 requires Node >=22.22.0, but CI still runs the Wasm build and tests on Node 20, leaving those jobs on an unsupported runtime.

2 open issues

• Run Rollup 5 jobs on a supported Node version · New
• Test rawId filtering with a wasm include pattern · New

1 file not reviewed

• pnpm-lock.yaml: Generated file

What changed in this PR

Adds Rollup 5 compatibility to the Wasm plugin, addressing attribute-encoded module IDs while retaining fallback behavior for earlier Rollup versions.

Changes:

• Uses rawId for filtering, file access, sync matching, and emitted-asset tracking.
• Adds import-attribute tests and disables tree-shaking in environment-specific tests.
• Extends the Rollup peer range and selects Rollup 5 for development.

File	Description
pnpm-workspace.yaml	Adds the shared Rollup 5 development catalog.
pnpm-lock.yaml	Locks Rollup 5 and its dependency resolutions.
packages/​wasm/​test/​test.mjs	Tests attributed imports and asset deduplication; adjusts environment tests.
packages/​wasm/​test/​fixtures/​attributes.js	Exercises execution of an attributed Wasm import.
packages/​wasm/​test/​fixtures/​attributes-and-plain.js	Imports one Wasm file with and without attributes.
packages/​wasm/​src/​index.ts	Handles attributed module IDs through rawId.
packages/​wasm/​package.json	Declares Rollup 5 support and updates the development dependency.

_{Review effort: Balanced}