fix: force the Storybook dep pre-bundle on every run instead of trusting the cache
Vite keys the Storybook project's dep cache on the lockfile and the config,
never on what the story graph imports. After a story or component gains an
import of an already-installed package, the cached bundle is still "valid",
Vite skips the scan, and the first request for the new package re-runs the
optimizer mid-run: the browser hash is bumped, a full-reload is sent that the
Vitest tester iframes ignore, and the `@storybook/react` renderer already
loaded in a live iframe keeps the old `?v=` for its lazy
`import("@storybook/react-dom-shim")`, so every story that iframe renders from
then on fails with "Failed to fetch dynamically imported module". The next run
is green because the cache has caught up.
`optimizeDeps.force: true` on the storybook project discards the cache up
front so the scanner crawls every story entry before the browser opens — the
cold path CI already takes on every PR. Measured: stale-cache 6/6 red on the
baseline, 6/6 green with the fix, 3/3 red reverted; ~0.8s per run.
Closes #2340
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PsmUAZ6aLUAFqenjJKSSRp
Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
parent
04024fe338
commit
5b9405fe8c
1 changed files with 25 additions and 0 deletions
|
|
@ -55,6 +55,13 @@ export function getViteBaseConfig() {
|
|||
// components import it at runtime (e.g. `protocolUtils`'s
|
||||
// `isInputRequiredResult` / `SUBSCRIPTION_ID_META_KEY`), so listing it
|
||||
// here keeps the dep graph stable across story files.
|
||||
//
|
||||
// That was one instance of a class, not the class: any package a story
|
||||
// or component starts importing after the cache was written is
|
||||
// discovered the same way, and pinning each one here would chase the
|
||||
// symptom. The `storybook` project in `vite.config.ts` now sets
|
||||
// `optimizeDeps.force` so every run re-scans the story entries up front
|
||||
// (#2340); this entry stays as the explicit include it always was.
|
||||
include: ["@modelcontextprotocol/client"],
|
||||
},
|
||||
};
|
||||
|
|
|
|||
Loading…
Reference in a new issue