feat: add next-repro CLI command #18787
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
yannbf
force-pushed
the
yann/sb-617-setting-up-the-generate-repro-script
branch
2 times, most recently
from
33888fb
to
7c2ec27
Compare
yannbf
force-pushed
the
yann/sb-617-setting-up-the-generate-repro-script
branch
from
7c2ec27
to
d282324
Compare
tmeasday
approved these changes
Jul 27, 2022
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.
Issue: N/A
What I did
New repro command, initial work containing default CRA only. Both JS and TS to test concurrency optimizations:
That yields the following structure:
How to test
yarn next-reproreprofolder in the root of the monorepoIf your answer is yes to any of these, please make sure to include it in your PR.