-
-
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 create-react-app --info #3380
Comments
This would help with the environment section of the issue template
But would require an update to CRA itself to work. |
Indeed - react native already has similar and it has worked amazingly well - you can see it in action in their issues. They even have a bot to auto close issues missing the template and environment. The only additional thing they would have to add is browser+version. react-native had the same issue where it was only available starting on version 0.48, but it was a good reason to get people to upgrade, and frequently solved their problem before even fully reporting the issue. If we believe it's worth it, I will make 2 PRs - one to add the CLI command, then another to add the updated instructions to the issue template, once the first PR is merged and there has been some time to update. |
I have a PR for the change to the CLI - #3408. I think we close this issue once that and my changes to the issue template get merged. |
I think its safe to close this issue now - both the implementation and docs are merged! |
This issue template seems to reserve a lot of space for trying to replicate and lock down issues from differing environments. Generally we want to make the process easier to ensure we get quality bug reports, so if the maintainers of the project agree, I'd like to integrate my envinfo package into CRA, the same way I already have for react-native.
Something like this:
create-react-app --info
in a project will yield something like this:I can add/subtract things from this report, and even nifty things like add auto add to clipboard.
Thoughts?
The text was updated successfully, but these errors were encountered: