Skip to content

Feature suggestion: npm run doctor #35

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

Closed
gaearon opened this issue Jul 20, 2016 · 4 comments
Closed

Feature suggestion: npm run doctor #35

gaearon opened this issue Jul 20, 2016 · 4 comments

Comments

@gaearon
Copy link
Contributor

gaearon commented Jul 20, 2016

If something’s messed up with your project setup, it would be great to have a way to repair it.
The most common problem I’ve seen in React apps is duplicate React installation.
It caused countless lost hours and people still bump into it: facebook/react#2402

We could offer npm run doctor that checks for common problems. As the first step, it would check npm ls | grep react and if there are two React installations, explain how to fix it (i.e. remove the nested one).

@mxstbr
Copy link
Contributor

mxstbr commented Jul 20, 2016

That's interesting. I would've thought this should be on the webpack layer?

@gaearon
Copy link
Contributor Author

gaearon commented Jul 20, 2016

Hm. Could do it that way too. Do you want to try?

@gaearon
Copy link
Contributor Author

gaearon commented Jul 23, 2016

@gaearon
Copy link
Contributor Author

gaearon commented Sep 3, 2016

Closing for no interest.

@gaearon gaearon closed this as completed Sep 3, 2016
@lock lock bot locked and limited conversation to collaborators Jan 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants