fix: build-storybook failure with Node 18 #398
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gndz07
changed the title
gndz07
force-pushed
the
fix/storybook-build
branch
2 times, most recently
from
2f52372 to
81ef6f1
Compare
paulocfjunior
approved these changes
Jan 13, 2023
paulocfjunior
force-pushed
the
fix/storybook-build
branch
from
029abb1 to
7e6c396
Compare
|
🎉 This PR is included in version 9.1.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The command
npm run build-storybookfailed when using Node v18 (as happened in this commit).It might be related to several issues regarding Storybook and Webpack version.
Possible related issues:
How to test
Run
npm run build-storybookcommand locally, make sure you are using Node v18.