eslint --init should offer to save custom configs
See original GitHub issueThe version of ESLint you are using. v7.12.1
The problem you want to solve. Copy/paste a config I want for all of my projects.
Your take on the correct solution to the problem.
eslint --init
should offer an option to use a saved configuration.
Are you willing to submit a pull request to implement this change? Yes
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Getting Started with ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >How to add a custom ESLint configuration to a Create React ...
In this post, we will look at ESLint integration on both JavaScript and TypeScript based React Projects created with Create React App (CRA) ......
Read more >How To Lint and Format Code with ESLint in Visual Studio Code
Activating or initializing ESLint will create an ESLint configuration file that will allow you to customize how ESLint works with your project.
Read more >ESLint: Everything You need to know about setting up a style ...
In the perfect world, the code should be indistinguishable from its ... npm install --save-dev eslint-config-prettier eslint-plugin-prettier.
Read more >Configure ESLint for Next.js - Devin Shoemaker
ESLint requires a config in the root of the project, which can be easily generated with the CLI. ... This command will prompt...
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
@tcppp, thank you for taking time to contribute to ESLint with this suggestion! We talked about it in today’s TSC meeting. Because
--init
is often used by developers who are new to ESLint or once at the start of a new project, we try to avoid having too many moving parts. Since this has a copy/paste alternative solution, we decided not to add this feature.TSC Summary: This proposal seeks to allow a way to save custom configs to be selected as part of
--init
. This would involve a way to specify which configs to include and then display them when--init
is used. This would require an RFC before implementation.TSC Question: Shall we accept this proposal?