René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"devtools-ui 0.7.0 breaks SSR boot with solid-js \u003c=1.9.12: `use` is not exported by solid-js/web server build","articleBody":"### TanStack Devtools version\n\n`@tanstack/devtools` 0.14.0 / `@tanstack/devtools-ui` 0.7.0 (still present in 0.14.1 / 0.7.1, the latest at time of filing)\n\n### Framework/Library version\n\nTanStack Start (`@tanstack/react-start` 1.168.x) + Vite 8 (rolldown) + `@cloudflare/vite-plugin`, solid-js 1.9.12 in the lockfile\n\n### Describe the bug\n\nUpgrading `@tanstack/devtools` 0.13.0 → 0.14.0 (which bumps the bundled `@tanstack/devtools-ui` 0.6.0 → 0.7.0) makes `vite dev` fail to boot in any app whose **SSR environment** processes devtools, when the resolved `solid-js` is ≤ 1.9.12:\n\n```\nError: Error during dependency optimization:\n\n[MISSING_EXPORT] \"use\" is not exported by \"node_modules/solid-js/web/dist/server.js\".\n   ╭─[ node_modules/@tanstack/devtools/node_modules/@tanstack/devtools-ui/dist/esm/components/theme.js:2:45 ]\n   │\n 2 │ import { createComponent, insert, template, use } from \"solid-js/web\";\n   │                                             ─┬─\n   │                                              ╰─── Missing export\n```\n\nThe dev server never starts, which also takes down every Playwright run driven by `vite dev`.\n\n### Root cause\n\n- `@tanstack/devtools-ui` **0.7.0** (PR #492, commit a46d1f5) wrapped `ThemeContextProvider`'s children in `\u003cspan style=\"display:contents\" ref={setContainer}>` so it can call `ensureDevtoolsStyles(element.ownerDocument)` (`src/components/theme.tsx`). The Solid compiler emits that `ref` as `use(setContainer, _el$)`, so the published ESM (`dist/esm/components/theme.js`) now imports `use` from `solid-js/web`. In 0.6.0 that file imported only `createComponent`.\n- Under the `node`/SSR export condition, `solid-js/web` resolves to `web/dist/server.js`. That server build exported **no `use` at all through solid-js 1.9.12**; solid-js **1.9.13** (2026-05-15) added it as a `notSup` stub (`notSup as use`).\n- `@tanstack/devtools-ui` declares `solid-js: >=1.9.7` (and `@tanstack/devtools` depends on `^1.9.9`), so resolvers happily keep ≤ 1.9.12 in existing lockfiles — a lockfile that worked with devtools 0.13.0 hard-fails right after the bump.\n\nClient-only setups never hit it (the browser build has always exported `use`), which is presumably why it shipped unnoticed. It surfaces wherever the SSR side bundles or import-validates devtools — e.g. TanStack Start with rolldown-vite's SSR dependency optimizer.\n\n### Steps to reproduce\n\n1. Lockfile with `solid-js@1.9.12` (any version ≥1.9.7 and ≤1.9.12 works) and `@tanstack/devtools@0.14.x`.\n2. Import devtools in an app whose Vite SSR environment processes it (TanStack Start default setup is enough).\n3. `vite dev` → `MISSING_EXPORT \"use\"` during SSR dependency optimization.\n\nOr minimally, in any Node ESM context resolving the server condition:\n\n```js\nimport { use } from 'solid-js/web'; // solid-js@1.9.12, server condition → SyntaxError/MISSING_EXPORT\n```\n\n### Suggested fix\n\nRaise the solid-js floor to `^1.9.13` in `@tanstack/devtools-ui`'s (and `@tanstack/devtools`'s) dependency ranges, so resolvers pull a solid-js whose server build has the `use` stub. Alternatively avoid the `ref` → `use` emission in output that gets loaded under the server condition.\n\nWorkaround for affected users: force-dedupe `solid-js` to ≥ 1.9.13 (we removed the stale nested resolutions from the lockfile so a single hoisted 1.9.15 serves everything; that fixes the boot).\n","author":{"url":"https://github.com/tombeckenham","@type":"Person","name":"tombeckenham"},"datePublished":"2026-08-20T03:26:05Z","url":"https://github.com/TanStack/devtools/issues/511"}