
Published under: Case Studies
5 min read
We just pushed ESLint v7.18.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.
f17c3c3
Update: check logical assignment operators in the complexity rule (#13979) (Milos Djermanovic)179a910
Fix: --init crash on question to upgrade/downgrade ESLint (fixes #13978) (#13995) (Milos Djermanovic)292b1c0
Fix: no-extra-parens false positive with let
identifier in for-loop (#13981) (Milos Djermanovic)672deb0
Docs: fix no-invalid-regexp docs regarding ecmaVersion (#13991) (Milos Djermanovic)f2687e7
Docs: update space-in-parens related rules (#13985) (Chris Brody)4a38bbe
Docs: space-in-parens examples with no arguments etc. (#13987) (Chris Brody)f6948f6
Docs: Update semantic versioning policy (#13970) (Nicholas C. Zakas)e3264b2
Upgrade: @eslint/eslintrc to improve error message for invalid extends (#14009) (Milos Djermanovic)9250d16
Upgrade: Bump lodash to fix security issue (#13993) (Frederik Prijck)78cb483
Chore: test foo( )
with space-in-parens option “always” (#13986) (Chris Brody)aeba5e5
Chore: fix typo (#13975) (Nitin Kumar)The latest ESLint news, case studies, tutorials, and resources.