Open jaydenseric opened 1 month ago
Related: https://github.com/lasselupe33/eslint-plugin-comment-length/issues/12 That package (specifically typescript eslint parser) is used for checking comments with code.
As mentioned by @yf-yang, typescript-eslint is used in several cases by this plugin. It might be possible to avoid this dependency altogether, which I will examine in the near future.
However, as typescript-eslint is also used to improve DX, I'd prefer waiting for typescript-eslint v8 to be released (currently in alpha), so that I can batch ESLint v9 support into a single run as I've got limited time to actively maintain this plugin. Fingers crossed that this will happen soon.
If no updates are seen within the next couple of weeks I might reconsider. :)
Just to add, the roadmap for v8 can be found here. The earliest v8 should be ready is around July, with the latest timeframe around September.
This dependency needs updating:
https://github.com/lasselupe33/eslint-plugin-comment-length/blob/1a381d6159f4b970e1091c7be04dde8cbcd1a3ff/rules/package.json#L30-L32
Otherwise, you can see problems like this when running
npm ls eslint
in a project with ESLint v9 setup:I'm not sure why
@typescript-eslint/utils
is a dependency; it seems like a good idea to avoid it in a plugin that's intended to be used in either TypeScript or non-TypeScript projects. It introduces all sorts of complexity.