-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
Docs: Improve vitest addon config snippets #32976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs: Improve vitest addon config snippets #32976
Conversation
📝 WalkthroughWalkthroughDocumentation snippet file updated to replace Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes
Possibly related PRs
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used📓 Path-based instructions (1)docs/**📄 CodeRabbit inference engine (.github/copilot-instructions.md)
Files:
🧠 Learnings (13)📓 Common learnings📚 Learning: 2025-09-17T08:11:04.287ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:04.287ZApplied to files:
📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.197ZApplied to files:
📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.197ZApplied to files:
📚 Learning: 2025-10-13T13:33:14.659ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
📚 Learning: 2025-09-17T08:11:47.196ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
🔇 Additional comments (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
View your CI Pipeline Execution ↗ for commit dce35e0
☁️ Nx Cloud last updated this comment at |
…ject-docs Docs: Improve vitest addon config snippets (cherry picked from commit b9695ea)
Relates #32895, as well as to 2 previous PRS: #32896, #32228.
Originally, in my issue above, I reported that an
extends: trueblock from the docs didn't work when it was insidedefineProject- it was then removed from the docs in #32896. However, it's an important part when you want to preserve configuration fromvite.config.ts(or any other shared config) - in my case, I needed to preserve some aliases, as well as some variables in thedefineblock. It lead me to understand whenextends: trueis used and when not, and how I can correctly add it to my project.extends: trueindeed cannot be a part ofdefineProject- TS reports that as an unknown key. Instead, it should be used with inline projects. Example from their docs:Okay then. But... vitest mention in their docs that:
How come?

That's because
defineProjectshould only be used when a project is extracted to its own<project>.vitest.config.tsfile. See how in their docsdefineProjectis only used in that case:How would you
extends: truein a project that is extracted to its own file then? Well, with its ownmergeConfigof the config you need. Here they show both cases:So, to sum it up - I think that
extends: trueshould be brought back to the docs examples, as its valuable. For that, we just need replacedefineProjectwith inline projects.What I did
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsMake 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/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>Summary by CodeRabbit