-
-
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
"npm start" error if there is a .babelrc file in parent folder #233
Comments
This is a babel-specific feature, see here: https://babeljs.io/docs/usage/babelrc#lookup-behavior We could add a Thanks for kicking off this discussion! |
Would adding Babel itself has a |
I think it should. |
Sounds straightforward, is this up for grabs? This needs to happen in both dev and prod, right? |
Ohh, nice one @insin! Feel free to submit a PR @alexzherdev! |
Done by the amazing @alexzherdev in #236! 👍 |
Anyone want to add a note about using |
|
Can you verify 0.2.0 alpha fixes this? #190 |
Remove tslint-loader from prod build (again)
if I have a folder named "React" or some other name.
run
create-react-app test-react
in folder Reactcd ./test-react
run
npm start
it works fine;but if I put a .babelrc file in folder "React"
echo "{presets: ['es2015']}" > ../.babelrc
and run
npm start
if will cause a error:
Failed to compile. Error in ./src/index.js Module build failed: Error: Couldn't find preset "es2015" relative to directory "/Users/forclan/Documents/Javascript/React" at Array.map (native) @ multi main
It seems that
react-scripts
will find a.babelrc
file the way up to "~"(if i put the .babelrc file in my home folder,it will generate the same error);The text was updated successfully, but these errors were encountered: