From 612ec6cce98f492913149e44e68af2bae801a68b Mon Sep 17 00:00:00 2001 From: meh Date: Sat, 15 Aug 2026 07:43:52 +0700 Subject: [PATCH 1/3] ci: retrigger after the base change From db9d7bcaafa534a5d7dc3d1f3d529085d851c6c1 Mon Sep 17 00:00:00 2001 From: meh Date: Sun, 16 Aug 2026 16:35:08 +0700 Subject: [PATCH 2/3] fix(oxc): 0.2.1, published through the workflow that builds every binding 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. --- packages/solid-layouts-oxc/package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/solid-layouts-oxc/package.json b/packages/solid-layouts-oxc/package.json index 01f35f6..3dd5e7e 100644 --- a/packages/solid-layouts-oxc/package.json +++ b/packages/solid-layouts-oxc/package.json @@ -1,6 +1,6 @@ { "name": "solid-layouts-oxc", - "version": "0.2.0", + "version": "0.2.1", "description": "The Layouts pre-pass for SolidJS, built on oxc", "license": "MIT", "type": "commonjs", From 1ff69caddc969157b102e6f042465d0e02683802 Mon Sep 17 00:00:00 2001 From: meh Date: Sun, 16 Aug 2026 17:05:56 +0700 Subject: [PATCH 3/3] fix(rsbuild-plugin): accept the oxc 0.2.1 that carries every binding 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. --- packages/rsbuild-plugin-solid-layouts/package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/rsbuild-plugin-solid-layouts/package.json b/packages/rsbuild-plugin-solid-layouts/package.json index d9d8b35..8783514 100644 --- a/packages/rsbuild-plugin-solid-layouts/package.json +++ b/packages/rsbuild-plugin-solid-layouts/package.json @@ -1,6 +1,6 @@ { "name": "rsbuild-plugin-solid-layouts", - "version": "0.2.0", + "version": "0.2.1", "description": "Rsbuild integration for the Solid Layouts library and application compilers", "license": "MIT", "type": "module", @@ -19,7 +19,7 @@ "index.d.ts" ], "dependencies": { - "solid-layouts-oxc": "0.2.0" + "solid-layouts-oxc": "^0.2.1" }, "peerDependencies": { "@rsbuild/core": ">=1.3.0"