-
-
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
Babel Error on start - clean app #8061
Comments
I have the same issue |
I experience the same issue. Worked fine a week ago. |
Same issue for all 25 of my students. |
Same |
This is happening to me as well |
Same for me, was working fine 2 hours ago |
|
Same here. |
Looks like it's because the npm cache hasn't been updated yet, it's a bug in should fix itself soon? |
The fix has been released 1 hour ago but it isn't downloaded by npm: npm/cli#545 |
Well... isn't that niffty. Thanks for the heads up! |
If you need it to work now and you cant wait for npm to be updated, you can run this: |
if you run |
Sounds like we this issue is out to the hands of this team. Thanks for all of the support my dudes! 😄 |
just as an update: Looks like npm got their stuff fixed. It should work now as intended. (I just verified it on my machine) npm steps:
As the create react app team likes to say... "Happy Hacking!" 😄 |
Describe the bug
I created a new/clean react app and on first run of the start script with no edits I get a Babel Error.
See below for my CLI outout.
Did you try recovering your dependencies?
Followed the Recommended fix steps and issue persists.
NPM Version: 6.13.1
Which terms did you search for in User Guide?
'npm start error'
'babel error'
'npm start babel error'
Environment
Steps to reproduce
npx create-react-app app-name
cd app-name
npm start
Expected behavior
Opens default react app in browser (no errors)
Actual behavior
Error output in CLI and Browser:
(see description for CLI Error output)
Reproducible demo
I didn't change anything from what is provide immediately after running create-react-app
The text was updated successfully, but these errors were encountered: