Currently all of our dependencies are defined as peerDependencies. I think that we can easily switch the following packages to real dependencies:
@typescript-eslint/eslint-plugin
@typescript-eslint/parser
eslint-plugin-react
eslint-plugin-react-hooks
Maybe even use ~ instead of ^ as a version prefix to only allow patch releases for automatic upgrading. New minor versions could introduce new rules that we don't want.
I'm not sure about eslint itself tho - I think that it should be left as a peerDependency.
Examples of popular eslint configs and their dependencies:
airbnb - mixed use of peer and normal dependencies
I want to:
Explanation or benefit
Currently all of our dependencies are defined as peerDependencies. I think that we can easily switch the following packages to real dependencies:
Maybe even use ~ instead of ^ as a version prefix to only allow patch releases for automatic upgrading. New minor versions could introduce new rules that we don't want.
I'm not sure about eslint itself tho - I think that it should be left as a peerDependency.
Examples of popular eslint configs and their dependencies: