Update eslint:recommended for 3.0.0
See original GitHub issueAs we always do with major releases, we should update eslint:recommended
to include any new rules we’ve added since 2.0.0 that flag potential errors.
Issue Analytics
- State:
- Created 7 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
Migrating to v3.0.0 - ESLint - Pluggable JavaScript Linter
js, we recommend upgrading to at least Node.js 4 as soon as possible. If you are unable to upgrade to Node.js 4 or...
Read more >3.0.0 - eslint - npm
An AST-based pattern checker for JavaScript.. Latest version: 8.23.1, last published: 10 days ago. Start using eslint in your project by ...
Read more >@eslint-recommended/eslint-config-typescript - NPM Package ...
Recommended ESLint Shareable Config for TypeScript. Version: 3.0.0 was published by munierujp. Start using Socket to analyze ...
Read more >eslint-plugin-markdown | Yarn - Package Manager
eslint 857.9kMIT3.0.0 vulns ... An ESLint plugin to lint JavaScript in Markdown code fences. ... f186730 ci: update github actions (#207) (Deepshika S) ......
Read more >eslint/eslint - Gitter
npm WARN eslint-plugin-react@6.10.3 requires a peer of eslint@^2.0.0 || ^3.0.0 but none is installed. You must install peer dependencies yourself.
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
👍 to removing
comma-dangle
from"eslint:recommended"
and therefore also consider moving it from Possible Errors to Stylistic IssuesI used
eslint --init
on a node project and noticedno-console
is enabled by default. This seems sensible for code that (also) runs in the Browser environment, but forenv.node
not so much.Could we disable this based on the environment parameters?
Doing it at run-time based on environment may be preferable as to avoid it being kept if a project adds env.browser later on. Alternatively, perhaps the config initializer can add
"no-console": 0
by default if env.node is set and env.browser is not.