Update issue template to include the --info flag

[bondz]

Document using the --info flag exposed by #3408 when reporting issues in CRA.

For platforms that have a built in command to pipe from terminal to clipboard (OSX and Windows), the suggested command copies the result to the clipboard automatically. Although, it also never prints the result to terminal for the user to see first, which might be a bummer, suggestions welcome.

For Linux users, there are different ways to pipe the result of a command to terminal, I'll leave it up to the user to use one.

[tabrindle]

Thanks @bondz. Was going to get to this after the holiday.

Do we need to keep the old commands?

Also envinfo can auto copy to clipboard built in via option as well get browser versions if we want to add this later on.

[tabrindle]

Also for the npx invocation of the command, it might be faster to use envinfo directly?

[bondz]

@tabrindle The reason I kept the old commands is based on the assumption that CRA does not advertize updating the CRA module itself, so, some users might not have it available.

Although, we could recommend that users are on that version like react-native does.

For the npx command, I opted to use CRA because the configuration info for CRA might diverge from that of envinfo in the future. That way, we wouldn't have to modify the issue template each time. It might be unnecessary if we recommend users be on a version of CRA with --info support.

The clipboard helper is a convenience especially for a user creating an issue and its explicit. Not sure if the default info command should automatically copy to clipboard, but would be nice since it works cross-platform on envinfo. Getting browsers would be a nice addition 👍

[gaearon]

I feel like since we advertise npx now, this is actually not super likely.

[Timer]

nit (sorry): macOS please

[gaearon]

Could you rebase please? I made some changes to the template that don't merge cleanly.

[bondz]

Done. Looks like its messed up now though. sigh.

[bondz]

Fixed.

[gaearon]

Shouldn’t these instructions come first? Users who follow our README will get an error.

[bondz]

I tested on macOS and Windows and it works. It errors on Linux without the xsel binary available.

I also tested it works on an ejected version of CRA. The react-scripts section of packages is missing.

#3859 should be available before this, otherwise, a version of Android Studio and XCode would be printed.

It took ~20sec to run on my Mac, even longer on Windows. There is no way to make npx use yarn yet see yarnpkg/yarn#3937

[bondz]

Closing in favour of #4375