Repository navigation
fix(storybook-builder): fix Node 22.18 - #2977
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 26fccca The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
bashmish
force-pushed
the
fix/storybook-builder-with-node-22.18
branch
from
August 7, 2025 20:30
f852503 to
4518368
Compare
bashmish
force-pushed
the
fix/storybook-builder-with-node-22.18
branch
from
August 7, 2025 20:41
4518368 to
cfcea9d
Compare
This file contains hidden or 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
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.
What I did
Manually set Node to 22.18 for storybook-builder tests (currently the default one used fro Node 22 was 22.17, so I had to be explicit to use a more recent one 22.18)
Checked that it breaks with Node 22.18