DNNCommunity / DNNCommunity/dnn-elements
Separate eslint-plugin into its own package
Open
bug
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I thought it would be a good idea that the eslint plugin be part of the main package but we need to ensure some peer dependencies which means if consumers do not use eslint, they can't install the recent packages.
It would be better if consumers need to get the eslint-plugin package only if they do use eslint.
Contributor guide
Assessment
This issue has not been assessed yet.