Enforce module boundaries via project.json eslint rule

[MJez29]

• I'd be willing to implement this feature (contributing guide)

Description

Add an @nx/enforce-module-boundaries rule equivalent that runs on project.json files

Motivation

Project dependencies can be added via implicitDependencies or createDependencies that violate dependency constraints. These bad dependencies will not be caught automatically because there is no typescript import associated with them. By having a rule that runs on project.json files it'll flag all dependency issues regardless of how the dependencies got added

Suggested Implementation

Most of the code can likely be refactored out and shared across rules

Alternate Implementations

[github-actions[bot]]

This issue has been automatically marked as stale because it hasn't had any activity for 6 months.
Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore.
If at this point, this is still an issue, please respond with updated information.
It will be closed in 21 days if no further activity occurs.
Thanks for being a part of the Nx community! 🙏

[MJez29]

Still valid

[FrozenPandaz]

I think this is valuable. The core team has been thinking of taking this behavior outside of ESLint so that it can support dependencies to projects of different languages.

How would people like to see this implemented?

[MJez29]

I think exporting a devkit function is a good place to start

export function isDependencyValid(projectGraph: ProjectGraph, moduleBoundaries: ModuleBoundaries, sourceProject: string, targetProject: string): boolean;

This will provide an entrypoint for non-eslint code to work with

From there Nx could take this a step further and provide a CLI command that will use this under the hood