fix(scripts-storybook): make sure to exclude our custom v9 babel preset from storybook babel-loader #27417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous Behavior
Introduction of
extendswith custom v9 preset withinbabelrcconfigs broke_processBabelLoaderOptions, thus griffel preset was used during storybook builds. While on pure v9 packages, things mostly still worked as expected cross project storybooks stopped working triggering following build errors:Failure for
@fluentui/react-migration-v8-v9:New Behavior
'@fluentui/scripts-babel/preset-v9'for storybookbabel-loader. This mitigates any issuesRelated Issue(s)