Move Babel and ESLint configuration into package.json after ejecting
See original GitHub issueUpdate: claimed by @montogeek
Currently we emit .babelrc
and .eslintrc
after ejecting.
This is better than embedding them in Webpack config like before, but still not ideal.
I think we should embed Babel and ESLint configuration into package.json
after ejecting.
We already do this for Jest.
Relevant settings in package.json
are called babel
and eslintConfig
.
This issue is up for grabs. If you’d like to work on it please comment below so that multiple people don’t work on the same thing. Please respect it if somebody has already commented, and don’t try to submit a PR before them.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:15 (12 by maintainers)
Top Results From Across the Web
Setting up a React app from scratch withWebpack, Babel and ...
setup IDE to check Eslint configurations. 1. Use — fix. Add the following line to package.json the file. "scripts": {
Read more >Babel module not being seen even though it is in package ...
I've tried deleting my package.json and node_modules folder and then running npm install . Nothing seems to work.
Read more >Configuration Files - ESLint - Pluggable JavaScript Linter
The first way to use configuration files is via .eslintrc.* and package.json files. ESLint automatically looks for them in the directory of the...
Read more >Wes Bos в Twitter: „@rafayepes @dan_abramov Yep - it's part of ...
Move Babel and ESLint configuration into package.json after ejecting · Issue #766 · facebook/crea... Update: claimed by @montogeek Currently we emit ...
Read more >Everything you need to know about react-scripts
In React apps, scripts are located in the package.json file's script ... or Babel configuration according to a specific need by ejecting the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Less dotfiles FTW in my opinion. It’s getting out of hand have a dotfile for all the things.
Seems to make more sense to have all the configuration live in a single spot with key value pairs rather than distributing the concern to all these different dotfiles.
I’m glad that my decision to not make yet another dotfile for jest is getting some traction 😃