Releases: EvgenyOrekhov/eslint-config-hardcore
v12.8.1
v12.8.0
Changes:
hardcore
- Set ECMAScript version to 2021
- Enable
ignoreDefaultValues
option forno-magic-numbers
ts-for-js
- Use
@typescript-eslint/no-shadow
instead ofno-shadow
- Use
@typescript-eslint/no-redeclare
instead ofno-redeclare
- Disable
@typescript-eslint/no-unnecessary-condition
since it requiresstrictNullChecks
compiler option
v12.7.0
v12.6.0
hardcore
v12.5.0
hardcore
- Update dependencies
hardcore/ts-for-js
- Add
@typescript-eslint/no-loss-of-precision
@typescript-eslint/no-unnecessary-boolean-literal-compare
- enable checking for comparing nullable booleans totrue
v12.4.0 - hardcore/ts-for-js
Use hardcore/ts-for-js
config to lint your JavaScript code with typescript-eslint
Take advantage of typescript-eslint's advanced type-aware rules (like @typescript-eslint/naming-convention
and @typescript-eslint/prefer-optional-chain
) without the need to switch to writing TypeScript!
Just follow these two easy steps.
v12.3.0
v12.2.0
- 77e2ca1 Enable
allowFinally
forpromise/catch-or-return
v12.1.0
- 00508d0 Enable
spaced-comment
andmultiline-comment-style
rules (both are autofixable)
v12.0.0 - eslint-plugin-prettier
I've been using Prettier in my projects, personal and work ones, for 1.5 years now.
It saved me and my colleagues countless hours of manually formatting our code.
It saved us countless hours of bickering about formatting rules.
This release of eslint-config-hardcore adds eslint-plugin-prettier.
Next time you run eslint --fix .
, all of your code will be reformatted.
But then you'll be free of manual formatting forever.
As a general advise, I recommend everyone adopt Prettier and use the default options.
Use it for formatting all files in your projects, not just JavaScript: prettier . --write
Breaking changes:
- 7c23dce Add eslint-plugin-prettier
- e11d63a Add eslint-plugin-ext
- 44f64ec Enable
unicorn/prevent-abbreviations
rule