Is it possible to have more readable package.json file?
See original GitHub issueThe title comes from this question: Why all of the configs are in the package.json file?
Why we have not separated these files:
.eslintrc
and.eslintignore
for ESLint configuration.babelrc
for having babel configuration.stylelintrc
for having style lint configuration.prettierrc
for having configuration of prettier.browserslistrc
for having browserify configuration- and etc.
If you are agreed, let me do these configurations. I will make them.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
package.json - npm Docs
Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...
Read more >Add custom metadata or config to package.json, is it valid?
Yes, you're allowed to add custom entries to package.json . Choose a key name: not already defined (details below); not reserved for future...
Read more >The package.json guide - Flavio Copes
The package.json file is a key element in lots of app codebases based on the Node.js ecosystem.
Read more >package.json Quick Start Guide | phoenixNAP KB
Learn how the package.json file lets you automatically manage various Node.js package metadata, such as project dependencies in this guide.
Read more >What Is package.json? | heynode.com
There are more fields than the ones we cover, and you can read about the rest in the documentation, but these are 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 FreeTop 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
Top GitHub Comments
@amerllica I have replied your comments, please review them. If any concerning, feel free to discuss with me, thank you.
Dear @wellyshen, Thanks for your comments. for the last time, please review the comments and after that, I will change my codes for the current PR.