-
-
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
Webpack: Fix sourcemap generation in webpack react-docgen-loader #26676
Webpack: Fix sourcemap generation in webpack react-docgen-loader #26676
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit fec5def. 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 2 targetsSent with 💌 from NxCloud. |
@@ -114,7 +114,10 @@ export default async function reactDocgenLoader( | |||
} | |||
}); | |||
|
|||
const map = magicString.generateMap({ hires: true }); | |||
const map = magicString.generateMap({ |
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.
Why did you remove the high resolution setting?
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 don't think it's that crucial. It now behaves like react-docgen in the vite builder. Usually, when using sourcemaps, it's enough to point to the line instead of the exact char position when the original files are in place. And since this was never working, I would start with the more performant variant and improve the source map detail level on request.
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.
Sure thing, let's just not forget that this setting was there in the first place!
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
…-docgen-sourcemap-generation Webpack: Fix sourcemap generation in webpack react-docgen-loader (cherry picked from commit eba6ed9)
Closes #26047
What I did
When
@storybook/addon-controls
was used (also part of@storybook/addon-essentials
), the sourcemaps weren't generated properly for Webpack5-based projects. This should be fixed now. The issue was that the react-docgen-loader wasn't configured properly to output proper sourcemaps.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
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>