-
-
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
Vite: Fix stats-plugin to normalize file names with posix paths #27218
Vite: Fix stats-plugin to normalize file names with posix paths #27218
Conversation
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.
🙌
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 0f899a9. 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. |
@@ -58,7 +59,7 @@ export function pluginWebpackStats({ workingDir }: WebpackStatsPluginOptions): W | |||
else { | |||
const relativePath = path.relative(workingDir, stripQueryParams(filename)); |
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.
Couldn't we just use path.posix.relative
here to use forward slashes, independently of the OS?
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.
@valentinpalkovic that is how I originally submitted this PR, until @shilman suggested using slash
to be consistent with how windows paths are already converted elsewhere. I don't mind either way, if you're able to decide between you which option is preferable?
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.
I see. Sorry that I haven’t followed the whole conversation! It’s fine then how it is!
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
…ts-json-posix-paths Vite: Fix stats-plugin to normalize file names with posix paths (cherry picked from commit abfcc9f)
Closes #27172
What I did
Updates the
normalize
function within thewebpack-stats-plugin
forbuilder-vite
to always normalize file names with posix path separators (/
).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!
storybook build --stats-json
name
andid
fields in thepreview-stats.json
file are using posix path separators (/
) and not windows separators (\\
)Documentation
MIGRATION.MD
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 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>