-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Vitest: Fix add command #28975
Vitest: Fix add command #28975
Conversation
…the test config from that Vite config file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 534fb2b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
export default defineWorkspace([ | ||
'${relative(dirname(browserWorkspaceFile), rootConfig)}', | ||
{ | ||
extends: '${viteConfig || ''}', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there is no viteConfig it now extends an empty string.
But in that case, I think we should just not extend anything
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also we want to make this a relative path, similar as the one above:
'${relative(dirname(browserWorkspaceFile), rootConfig)}',
]); | ||
` | ||
]); | ||
`.replace(/\s+extends: '',/, '') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I see
What I did
Fixes the
add
command for addon-vitest to write a workspace config file if we find a vite.config.ts/js file, and extend our test config from that file. Removed theisolate: false
option because it causes errors regarding empty story files (no tests).Also cleans up a few smaller issues.
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/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 pull request has been released as version
0.0.0-pr-28975-sha-d3d6fd2e
. Try it out in a new sandbox by runningnpx storybook@0.0.0-pr-28975-sha-d3d6fd2e sandbox
or in an existing project withnpx storybook@0.0.0-pr-28975-sha-d3d6fd2e upgrade
.More information
0.0.0-pr-28975-sha-d3d6fd2e
vitest-addon-fixes
d3d6fd2e
1724757346
)To request a new release of this pull request, mention the
@storybookjs/core
team.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=28975
Greptile Summary
This PR enhances the Vitest addon's postinstall script for Storybook, improving compatibility and configuration handling.