Uh oh!
There was an error while loading. Please reload this page.
add envinfo package, —info flag - #3408
Conversation
gaearon
commented
Nov 6, 2017
Let's also check for duplicate |
tabrindle
commented
Nov 6, 2017
That's a great idea. Will add. |
tabrindle
commented
Nov 8, 2017
With the new option You can actually test this in an existing CRA with |
bondz
commented
Nov 12, 2017
Still doesn't have a The test failure isn't related to this PR. |
tabrindle
commented
Dec 12, 2017
Is there anything I can do to trigger the test build for react-scripts-dangerous? |
bondz
commented
Dec 13, 2017
Ping @Timer |
bondz
commented
Dec 13, 2017
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. |
Timer
commented
Dec 13, 2017
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. |
gaearon
commented
Jan 9, 2018
Looks like a good start. Let's get this in and iterate. |
gaearon
commented
Jan 15, 2018
This is out. |
bondz
commented
Jan 15, 2018
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 --infowhich should print the following: