Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add option to auto-disable if no `.eslintrc`
See original GitHub issueWhen I open a repo that doesn’t use eslint, I get an obtrusive output error from this plugin, requiring me to manually disable it every single time.
It’d be really nice to have an option for this plugin to auto-disable itself if no .eslintrc is present in the repo (and/or if it’s not in the dependencies)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:25
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Command Line Interface - 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 >Turning off eslint rule for a specific file - Stack Overflow
1) Disabling "All rules" · You can go with 1.2 and add /* eslint-disable */ on top of the files, one by one....
Read more >@volvo-cars/eslint-config - npm
Lint errors should not be disabled with inline comments, except as a temporary measure after enabling new stricter rules. Install. yarn add @ ......
Read more >How to disable ESLint for some lines, files or folders
To temporarily turn off ESLint, you should add a block comment /* eslint-disable */ before the lines that you're interested in:.
Read more >ESLint | IntelliJ IDEA Documentation - JetBrains
To configure ESLint automatically in the current project, open the Settings/Preferences dialog ( Ctrl+Alt+S ), go to Languages & Frameworks | ...
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
Just saying, this would align with what prettier has:
The major problem is that this put the extension into a catchup with the ESLint library. If they add a new config location or a new way to define the config we need to honor this. This is why in general I stay away from this and such a feature can only go behind a flag and must be off by default.