Parser is a dependency but eslint-plugin is a peer dependency

[Methuselah96]

Is there a reason why @typescript-eslint/eslint-plugin is a peer dependency, but @typescript-eslint/parser is a dependency? I'd like for them both to be peer dependencies so that I can use matching versions.

[leethree]

agree. also @typescript-eslint/parser shouldn't be pinned to a specific version (as I commented on #153 (comment)). otherwise users won't be able to match the version between parser and plugin.

[Djaler]

@iamturns can you please change this?

[iamturns]

The reason @typescript-eslint/eslint-plugin is a peer dependency, is because all ESLint plugins must be installed locally. This is a limitation within ESLint itself. See RFC and progress

To help with this, I've just removed the peerDependency (see #187). This allows more flexibility with the version of eslint-plugin you want to install. Also, the dependencies are unpinned, so that you can keep @typescript-eslint/eslint-plugin and @typescript-eslint/parser versions in sync too.

Hope this helps. Cheers!

[iamturns]

🎉 This issue has been resolved in version 12.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[utrumo]

This issue has been resolved in version 12.0.1

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot

@typescript-eslint/parser must also be removed from dependencies for keeping @typescript-eslint/eslint-plugin and @typescript-eslint/parser versions in sync too. This module is already in peer dependencies eslint-config-aribnb and eslint-config-airbinb-base