@spotify/eslint-config - npm Package Versions

9.0.1 (2021-02-21)

Bug Fixes

• update ts-jest config (052a888)

9.0.0 (2020-10-26)

Bug Fixes

• bl (526a096)
• incorporate overrides for new typescript-eslint rules (81b7111)
• relax no-use-before-define rule (ee719aa)
• sync @typescript-eslint versions across repo (fb20119), closes #555

Features

• @spotify/best-practices/no-discouraged-words: switch to warn (f1aed8c)
• use TypeScript 4 (bbf1164), closes #487 #252

BREAKING CHANGES

• must upgrade to TypeScript 4 as a consumer; new tsconfig takes advantage of incremental + noEmit

8.1.1 (2020-09-22)

Bug Fixes

• update eslint-plugin to allow for @typescript-eslint/parser@4 (0363558)

8.1.0 (2020-09-08)

Features

• eslint-spotify: added eslint-plugin package w/ best-practices/no-discouraged-words (ddbbadc)

8.0.2 (2020-07-15)

Bug Fixes

• eslint-config-react: fix peer dependency on eslint-plugin-react-hooks (8591423)

8.0.1 (2020-07-02)

Bug Fixes

• eslint-config-typescript: turn off naming-convention (ed5eec3)

8.0.0 (2020-06-23)

Features

• commitlint: v9 (2709cb8)
• eslint: v7 (55ebb7f)
• eslint-plugin-jest: minor bump (e1fef3b)
• jest: v26 (14c37a8)
• jest-junit: v11 (1ef34c4)
• semantic-release: minor bump (ded14f4)
• typescript-eslint: upgrade to latest to support type export syntax (688324b)
• typescript-eslint/eslint-plugin: v3.4.0 (195400a)

BREAKING CHANGES

• commitlint: 'improvement' type will now be rejected by this config.
• eslint: see release notes for eslint v7
• jest-junit: see jest-junit 11 release notes
• jest: See jest 26 release notes
• typescript-eslint: The camelcase rule was deprecated in typescript-eslint. I've tried to replace it with an equivalent naming-convention rule config. I question if we should have this at all.

7.0.1 (2020-05-15)

Bug Fixes

• web-scripts: unknown command options were parsed twice (d30364b), closes #341

7.0.0 (2020-04-28)

• major release- 7.0.0 (#318) (29509b4), closes #318 #314 #312 #310

BREAKING CHANGES

• running web-scripts without arguments exits code 1 now instead of exiting 0

• prettier 2.0 may introduce breaking changes

• prettier 2.0 may introduce breaking changes

• improvement(web-scripts): make stylecheck and typecheck default for lint

the lint script will now default typechecking and stylechecking to true by default. You may shut these off with --no-typecheck and --no-stylecheck.

• Users who have projects incompatible with TypeScript checks or with projects that do not user prettier will now fail yarn lint.

6.2.0 (2020-04-04)

Features

• web-scripts: allow custom lint-staged (#276) (49324dc)