Decouple @nrwl/eslint-plugin-nx version from the rest of NX? #15814
ShayDavidson
started this conversation in
Feature Requests
Replies: 1 comment
-
Hey, nobody has responded about this for more than a year. Can we have someone from the NX team look at this? it's still a major problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're extensive users of NX, but one of our major pain points is around
@nrwl/eslint-plugin-nx
. I'll illustrate why:@typescript-eslint/eslint-plugin
in order to be able to parse new syntax.@nrwl/eslint-plugin-nx
then needs an upgrade as well, because itspeerDeps
are not supporting the new version of@typescript-eslint/eslint-plugin
.Any thoughts on this?
Possible solutions would be to decouple the plugin version from the NX version, or alternatively support a major version of
@typescript-eslint/eslint-plugin
in itspeerDeps
(and not a limited minor-version range like today).Note that we encounter this issue even when we just want to upgrade
@typescript-eslint/eslint-plugin
for a new rule or capability. Having to upgrade entire NX for this is cumbersome.Beta Was this translation helpful? Give feedback.
All reactions