-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add envinfo package, —info flag #3408
Conversation
Let's also check for duplicate |
That's a great idea. Will add. |
With the new option
You can actually test this in an existing CRA with |
Still doesn't have a The test failure isn't related to this PR. |
Is there anything I can do to trigger the test build for react-scripts-dangerous? |
Ping @Timer |
Whaat! That's a bummer @Timer. Was really helpful but doesn't make sense if it costs you that much. Thanks for building it. Maybe we can find someone willing to host it later. |
I think there was just some bug that caused the lambdas to run rampant; eventually when I have some free time I'll adjust it to prevent this from happening again. |
Looks like a good start. Let's get this in and iterate. |
This is out. |
See #3797 |
* add envinfo package, —info flag * update envinfo to use new duplicates option
I realize the file says not to modify the createReactApp.js, but a better way to do this did not occur to me. If there is a better way, I am certainly open to it.
To help the issue process and better narrow down environment and version issues, I have added
create-react-app --info
which should print the following: