-
-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Comments
That's interesting. I would've thought this should be on the webpack layer? |
Hm. Could do it that way too. Do you want to try? |
Closing for no interest. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 checknpm ls | grep react
and if there are two React installations, explain how to fix it (i.e. remove the nested one).The text was updated successfully, but these errors were encountered: