Skip to content

fix(rsbuild-plugin): accept the oxc 0.2.1 that carries every binding - #6

Merged
pathscale merged 3 commits into
masterfrom
fix/plugin-oxc-range
Aug 16, 2026
Merged

fix(rsbuild-plugin): accept the oxc 0.2.1 that carries every binding#6
pathscale merged 3 commits into
masterfrom
fix/plugin-oxc-range

Conversation

@pathscale

Copy link
Copy Markdown
Owner

The plugin pinned solid-layouts-oxc to an exact 0.2.0, so a consumer asking for 0.2.1 still got a nested 0.2.0 installed beneath the plugin, and that nested copy is the one the plugin actually loads.

0.2.0 was published by hand from a macOS laptop and carries only the darwin-arm64 binary, so every Linux build fails with Cannot find module 'solid-layouts-oxc-wasm32-wasi' no matter which version the consumer hoists. That is the current failure on pathscale/ui#242.

A caret range lets the workflow-built 0.2.1, which carries every target, satisfy the plugin too.

Needs a rsbuild-plugin-solid-layouts-v0.2.1 tag after merge to publish.

🤖 Generated with Claude Code

meh added 3 commits August 16, 2026 17:14
…ding

0.2.0 went to npm by hand and carried one `.node`: the darwin-arm64 binary
that happened to be in the working tree. `solid-layouts-oxc` ships its
bindings inside the main package rather than as platform sub-packages, so a
Linux consumer resolves nothing and fails at import:

    Cannot find module './solid-layouts-oxc.linux-x64-gnu.node'

That is what `@pathscale/ui`'s CI hit on every run, while the same command
passed on the machine the package was published from.

`release-oxc.yml` already builds all three targets on their own runners and
refuses to publish a partial set. npm will not let 0.2.0 be replaced, so this
is 0.2.1 through that workflow, which is the path that was skipped.
The plugin pinned solid-layouts-oxc to an exact 0.2.0, so a consumer asking
for 0.2.1 still got a nested 0.2.0 installed beneath the plugin, and that is
the copy the plugin loads. 0.2.0 was published by hand from a macOS laptop and
carries only the darwin-arm64 binary, so every Linux build failed on a missing
wasm32-wasi module no matter which version the consumer hoisted.

A caret range lets the workflow-built 0.2.1, which carries every target,
satisfy the plugin as well.
@pathscale
pathscale force-pushed the fix/plugin-oxc-range branch from 51e1d2b to 1ff69ca Compare August 16, 2026 10:14
@pathscale
pathscale merged commit a10bd1b into master Aug 16, 2026
4 checks passed
@pathscale
pathscale deleted the fix/plugin-oxc-range branch August 16, 2026 10:14
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.

1 participant