| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
@tanstack/devtools declares `solid-js: >=1.9.7` as a peer dependency, so a full re-resolution dedupes it onto the workspace's solid-js@2.0.0-rc.0 (introduced by #495 for the Rsbuild Solid example) instead of its own `solid-js: ^1.9.9` dependency. Solid 2 dropped `onMount`/`batch`/`on`/ `getListener` and the `./web` subpath export, breaking the build. Declaring solid-js explicitly pins this example's subtree back to 1.x without touching the Solid example.
| Back | FazBrowse Home | New Git URL |
Why
The rspack ecosystem CI run fails at build:rsbuild on rsbuild/tanstack-start with 64 module linking errors:
@tanstack/devtools declares solid-js: >=1.9.7 as a peer dependency. Since #495 introduced solid-js@2.0.0-rc.0 into the workspace, a full re-resolution (which ecosystem CI triggers by injecting @rspack/* overrides) dedupes that peer onto 2.0.0-rc.0 instead of the package's own solid-js: ^1.9.9 dependency. Solid 2 removed onMount / batch / on / getListener and the ./web subpath export, so the devtools bundle no longer links.
Before / after, same install (pnpm install --prefer-frozen-lockfile with @rspack/* overrides injected):
What
Declare solid-js: ^1.9.9 in rsbuild/tanstack-start, so this example provides the peer itself and its subtree stays on Solid 1.x. The Solid 2 RC in rsbuild/solid is untouched.
Rejected alternatives: dedupePeers: false (does not change the resolution), and a workspace-wide solid-js override (would downgrade the Solid example and undo #495).
Verified locally by running the full ecosystem CI sequence — build:rspack:eco-ci, test:rspack:eco-ci, build:rsbuild, build:rsdoctor, build:rspress, build:rslib — plus pnpm lint.