Add support for Nx-style "enforce module boundaries" rule

[toasty-kj]

I would like to request a new lint rule similar to Nx's enforce module boundaries for Biome.

🚧 Limitations of noRestrictedImports

The current noRestrictedImports rule operates on a blacklist approach, specifying modules that should not be imported. However, in monorepo environments, it's often more effective to define and enforce allowed import paths (a whitelist approach) to maintain clear boundaries between modules.

For instance, Nx's enforce-module-boundaries rule allows developers to:

• Define tags for projects and specify allowed dependencies between them.

• Restrict imports based on these tags, effectively creating a whitelist of permissible dependencies.

• Prevent circular dependencies and enforce architectural constraints.
  fs.usda.gov

These capabilities are crucial for maintaining scalable and maintainable codebases, especially as projects grow in complexity.

✅ Proposal

I propose introducing a new rule in Biome that mirrors the functionality of Nx's enforce-module-boundaries. This rule would:
timdeschryver.dev

Allow defining project tags or identifiers.

Enable specifying allowed import paths based on these tags.

Provide mechanisms to prevent undesired dependencies and enforce module boundaries.

Implementing such a rule would empower developers to maintain clear architectural boundaries within their codebases, leading to better scalability and maintainability.

🔗 References

• Nx: Enforce Module Boundaries

• Biome: noRestrictedImports Rule

related rules

• https://biomejs.dev/linter/rules/no-restricted-imports/
• https://typescript-eslint.io/rules/no-restricted-imports/

discussions

• Support Biome as formatter nrwl/nx#21045 (comment)

Thank you for considering this suggestion!

[ematipico]

@toasty-kj many users might not know (I'm one) what rule you're talking about.

I would suggest expanding your suggestion with few links and snippets, so we can understand better what you're suggesting.

In V2 we're about to ship this rule, but I'm not sure if it's related: https://next.biomejs.dev/linter/rules/no-private-imports/

[toasty-kj]

@ematipico

Thank you for your response!
The rule I’m referring to is similar to Nx’s enforce module boundaries rule.
It allows you to define boundaries between different modules or libraries in a monorepo, and restricts imports between them according to a configuration.
For example, you can prevent certain modules from importing code from other modules, or only allow imports from specific layers.
This helps maintain a clean architecture and prevents unwanted dependencies.
It would be great if Biome could support a similar feature, where we can specify these boundaries and constraints for module imports.
Thank you for considering this suggestion!

[hrasekj]

Actually I am looking for similar rule too. When using hexagonal architecture, you like to restrict import from, for example infrastructure/ into domain/, because it violates the architectural principle.

I was looking into rule noRestrictedImports but i don't think it's possible to achieve it.

.
└── apps
    └── private-api
        └── src
            ├── application
            │   ├── dtos
            │   └── use-cases
            ├── domain
            │   ├── entities
            │   ├── errors
            │   ├── repositories
            │   ├── services
            │   └── value-objects
            ├── infrastructure
            │   ├── http
            │   │   ├── controllers
            │   │   ├── middleware
            │   │   ├── routes
            │   │   └── validators

[chiragmRoado]

+1 here. I am also looking for this rule to be added soon.