-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Addon-docs: Fix babel-loader resolution based on builder #16752
Conversation
…e the proper version of babel-loader
☁️ Nx Cloud ReportCI ran the following commands for commit 64cdf45. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
const { builder = 'webpack4' } = await options.presets.apply('core', {}); | ||
|
||
const resolvedBabelLoader = require.resolve('babel-loader', { | ||
paths: [require.resolve(`@storybook/builder-${builder}`)], // FIXME!!! |
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.
What if the builder
is storybook-builder-vite
? Also what about the FIXME
?
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.
fixme can be removed, it's fixed.
I didn't think of the storybook-builder-vite
.
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! Thanks @ndelangen
Issue: #15336
What I did
resolve the
core
field via preset.applyread used builder so we resolve the proper version of babel-loader
How to test