Addon Vitest: Use its own cache directory

[yannbf]

Closes #31431

What I did

When using Storybook with other browser mode projects, the cache was getting corrupted as each Vitest instance needs its own cache, and dependency optimization from Storybook was affecting other project's cache. This PR makes it so that each Storybook vitest workspace has its own unique cache directory.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Modified the Vitest plugin to ensure each Storybook workspace uses a unique cache directory based on the config directory path hash, preventing cache corruption when running multiple Vitest instances simultaneously.

• Added cache directory configuration in code/addons/vitest/src/vitest-plugin/index.ts using config path hash
• Fixed issue where multiple Vitest instances were sharing and corrupting each other's cache
• Resolved test hanging/failing issues when running Vitest with multiple browser mode workspaces

[greptile-apps]

LGTM

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e5912a7.

Command	Status	Duration	Result
nx run-many -t build --parallel=3	✅ Succeeded	1m 42s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-05-12 07:29:36 UTC