0
Fork 0
mirror of https://github.com/TanStack/router.git synced 2026-11-16 19:38:07 +00:00
router/e2e/solid-start/css-modules/package.json
Sheraff 0517895892
build: one sass in the workspace so every package resolves the same vite
vite's optional peers `sass` and `sass-embedded` are resolved from whatever
versions exist anywhere in the lockfile graph. Two sass versions were in the
graph: 1.97.2 (the `^1.97.2` devDependency of the three Start css-modules
e2e apps) and 1.105.1 (pulled by `sass-embedded`, which
`@rsbuild/plugin-sass` brings into e2e/react-start/css-modules). Importers
resolved at different times got different vite peer variants: compiler-test-
utils, react-start-rsc and eslint-plugin-start got vite(sass@1.105.1), the
rest vite(sass@1.97.2). Two copies of vite break Start's
`isRunnableDevEnvironment` (instanceof) check, so Start's dev server
middleware never ran in the compiler test dev servers.

The css-modules e2e apps now ask for sass ^1.105.1, the version sass-embedded
already uses; the graph has one sass and one vite@8.3.4 (esbuild 0.28.2)
variant.

With Start's dev middleware working, the client-rendered route HMR test
turns it off explicitly (it serves index.html, not Start's SSR); the Start
dev-server harness accepts the Vite plugin options for that.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-18 18:00:16 +02:00

32 lines
1,014 B