CLI: Default new vite projects to storyStoreV7

[IanVS]

Issue:

What I did

The vite builder benefits greatly from the on-demand story store, especially in dev-mode where modules are all sent to the browser unbundled (for better HMR and faster server startup). In large vite storybook apps, this can mean thousands of network requests, which can take some time for the browser to process, causing a longer time-to-interactive. (Note, this isn't a problem in built storybooks, since vite bundles them with rollup to avoid this problem).

Furthermore, the new store is much more reliable and less likely to encounter bugs and subtle differences between the vite and webpack builders. A PR, storybookjs/builder-vite#303, is currently open which would allow the use of the new store while not lazy-loading, in case users prefer or require that approach.

How to test

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps?
• Does this need an update to the documentation?

I'm not sure how the cli is currently tested, other than in e2e tests, which do not use the vite builder (maybe we should add a few?)

But, I did build my changes, create a new vite project, and run the changed cli against it, and verified that features: {storyStoreV7: true} was in the generated config.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 9630843. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx run-many --target=prepare --all --parallel --max-parallel=15 -- --optimized

---

Sent with 💌 from NxCloud.

[shilman]

LGTM!