CLI: Fix Nextjs project detection#24346
Merged
Merged
Conversation
8aabddd to
f077780
Compare
ndelangen
approved these changes
Oct 2, 2023
valentinpalkovic
approved these changes
Oct 2, 2023
f077780 to
6ee8dca
Compare
20 tasks
storybook-bot
pushed a commit
that referenced
this pull request
Oct 3, 2023
CLI: Fix Nextjs project detection (cherry picked from commit 5c308f7)
Merged
4 tasks
storybook-bot
pushed a commit
that referenced
this pull request
Oct 3, 2023
CLI: Fix Nextjs project detection (cherry picked from commit 5c308f7)
storybook-bot
pushed a commit
that referenced
this pull request
Oct 3, 2023
CLI: Fix Nextjs project detection (cherry picked from commit 5c308f7)
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.
Closes #
What I did
Nextjs recently changed the way they generate projects, by defining
latestas the version ofnext. We had a logic in place when detecting the project type which would fail in this scenario, leaving the CLI hanging forever, and also affecting users because it would not be able to detect Nextjs. This PR fixes that and setsdebugas default when generating sandboxes, so it saves us time to figure out what is going on.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
No need.
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.tsMake 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/coreteam 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>