Skip to content

Releases: ezcater/ezcater-js-toolkit

eslint-config-ezcater-typescript@6.0.0

What's Changed

Breaking changes

The following were added as peer dependencies:

  • eslint-plugin-import
  • @typescript-eslint/eslint-plugin
  • @typescript-eslint/parser

This means that users are now expected to add them. Example:

yarn add -D eslint-plugin-import @typescript-eslint/eslint-plugin @typescript-eslint/parser

Full Changelog: https://github.com/ezcater/ezcater-js-toolkit/compare/eslint-config-ezcater-react@6.0.0...eslint-config-ezcater-typescript@6.0.0

eslint-config-ezcater-react@6.0.0

What's Changed

Breaking changes

The following were added as peer dependencies:

  • eslint-plugin-import
  • eslint-plugin-filenames
  • eslint-plugin-jest
  • eslint-plugin-jsx-a11y
  • eslint-plugin-react
  • eslint-plugin-react-hooks

This means that users are now expected to add them. Example:

yarn add -D eslint-plugin-import eslint-plugin-filenames eslint-plugin-jest eslint-plugin-jsx-a11y eslint-plugin-react eslint-plugin-react-hooks

Full Changelog: https://github.com/ezcater/ezcater-js-toolkit/compare/eslint-config-ezcater-base@6.0.0...eslint-config-ezcater-react@6.0.0

eslint-config-ezcater-base@6.0.0

15 Feb 21:20
Compare
Choose a tag to compare

What's Changed

Breaking changes

eslint-plugin-import was added as a peer dependency, which means that users are now expected to add it. Example: yarn add -D eslint-plugin-import

Full Changelog: https://github.com/ezcater/ezcater-js-toolkit/compare/eslint-config-ezcater-typescript@5.0.1...eslint-config-ezcater-base@6.0.0

eslint-config-ezcater-typescript@5.0.1

eslint-config-ezcater-typescript@5.0.0

Breaking changes

  • Replaced eslint-config-ezcater-react with eslint-config-ezcater-base. Consumers are expected to add eslint-config-ezcater-react separately if react linter rules are necessary.
  • Drop support for eslint-plugin-prettier, which is no longer recommended by Prettier. This is a breaking change because if consumers have any code comments including prettier/prettier eslint will now fail. Consumers are now expected to run prettier --check in CI if they want to keep the code quality validation. It's recommended to use prettier --write in lint-staged if you want to auto-format code and or use VSCode Prettier extension.
  • @typescript-eslint packages now require typescript version greater than 3.8

What's changed

eslint-config-ezcater-react@5.0.0

Breaking changes

  • Upgrade to eslint-config-ezcater-base@5 which drops support for eslint-plugin-prettier. This is a breaking change because if consumers have any code comments including prettier/prettier eslint will now fail. Consumers are now expected to run prettier --check in CI if they want to keep the code quality validation. It's recommended to use prettier --write in lint-staged if you want to auto-format code and or use VSCode Prettier extension.
  • Remove @babel/core and @babel/eslint-parser as dependencies. Consumers will now be expected to add their own eslint parser if they need it.

What's Changed

Full Changelog: https://github.com/ezcater/ezcater-js-toolkit/compare/eslint-config-ezcater-base@5.0.1...eslint-config-ezcater-react@5.0.0

eslint-config-ezcater-base@5.0.1

13 Apr 18:03
Compare
Choose a tag to compare

eslint-config-ezcater-base@5.0.0

30 Mar 21:55
Compare
Choose a tag to compare

What's Changed

Breaking changes

  • Drop support for eslint-plugin-prettier, which is no longer recommended by Prettier. This is a breaking change because if consumers have any code comments including prettier/prettier eslint will now fail. Consumers are now expected to run prettier --check in CI if they want to keep the code quality validation. It's recommended to use prettier --write in lint-staged if you want to auto-format code and or use VSCode Prettier extension.

eslint-config-ezcater-typescript@4.0.1

What's Changed

@ezcater/ez-scripts@2.0.1

10 Mar 20:00
Compare
Choose a tag to compare

What's Changed

Full Changelog: https://github.com/ezcater/ezcater-js-toolkit/commits/@ezcater/ez-scripts@2.0.1