Support resolving custom ESLint rules in projects outside of the workspace-rules-project mechanism

[koliveira15]

Support resolving custom ESLint rules outside of workspace-rules-project

Summary

Allow Nx to resolve custom ESLint rule plugins from other projects in the repo without requiring:

• a dedicated workspace-rules-project (not meant for publishing)
• publishing beta/alpha versions to npm/Verdaccio & dog fooding
• symlinks
• lint targets depending on build targets

This is especially important with ESLint v9 flat configs (eslint.config.js) and when workspaces linking isn’t available.

Problem

Today, if I put rules in packages/my-package, I can’t reuse them in other project configs unless I:

• build & copy the package to node_modules (either manually or via lint dependsOn build configurations)
• publish to npm
• use the workspace rules mechanism (prefixes all rules with workspace-, which makes it difficult to know where the rule came from)

Proposal

ESLint configs should import rules in the same workspace the same way a consumer of my package would:

import rules from '@org/my-package/eslint-rules'; // lives in packages/my-package

export default [
  {
    plugins: { org: rules },
    rules: { 'org/my-custom-rule': 'error' }
  }
];

Current workspace-rule resolution logic:

• resolve-workspace-rules
• registerTsProject

[AndrewRedican]

We were also hoping this could be accomplished in NX. Thanks for raising this feature request.

[GaddMaster]

Do it :)

[leosvelperez]

@koliveira15 thanks for the request!

We're looking into this and will have updates soon. It can't be done as proposed (importing directly), but a helper would be provided to resolve the rules and would be used instead of a direct import.

[theandrewlane]

This would be so convenient 🙏