ESLint Plugin Boundaries

Enforce architectural boundaries in your JavaScript and TypeScript projects.

ESLint Plugin Boundaries is an ESLint plugin that helps you maintain clean architecture by enforcing boundaries between different parts of your codebase. Define your architectural layers, specify how they can interact, and get instant feedback when boundaries are violated.

• Architectural Enforcement: Define element types and dependency rules that match your project's architecture
• Flexible Configuration: Adapt the plugin to any project structure. It works with monorepos, modular architectures, layered patterns, and more
• Real-time Feedback: Get immediate ESLint errors when imports violate your architectural rules

Documentation

The full documentation is available on the JS Boundaries website.

Key Sections

• Overview - Introduction to the plugin and its core concepts
• Quick Start - Set up the plugin in 5 minutes
• Setup Guide - In-depth configuration guide
  • Define Elements
  • Use Element Selectors
  • Configure Rules
  • Global Settings
• Rules Reference - Complete documentation for all available rules
• TypeScript Support - Use with TypeScript projects

Quick Example

Install the plugin using npm:

npm install eslint eslint-plugin-boundaries --save-dev

Define your architectural elements:

import boundaries from "eslint-plugin-boundaries";

export default [
  {
    plugins: { boundaries },
    settings: {
      "boundaries/elements": [
        { type: "controllers", pattern: "controllers/*" },
        { type: "models", pattern: "models/*" },
        { type: "views", pattern: "views/*" }
      ]
    }
  }
];

Define your dependency rules:

{
  rules: {
    "boundaries/element-types": [2, {
      default: "disallow",
      rules: [
        { from: "controllers", allow: ["models", "views"] },
        { from: "views", allow: ["models"] },
        { from: "models", disallow: ["*"] }
      ]
    }]
  }
}

Now ESLint will catch violations:

// In src/models/model.js
import View from "../views/view"; // ❌ Error: Architectural boundary violated

Contributing

To everyone who has opened an issue, suggested improvements, fixed bugs, added features, or improved documentation: Thank you. Your contributions, no matter how small, make a real difference. Every bug report helps us improve, every feature request guides our roadmap, and every pull request strengthens the project.

Special recognition goes to those who have contributed code to the project. Your technical contributions are the foundation of what makes this plugin valuable to the community.

Want to contribute? We'd love to have you! Here are some ways to get involved:

• Report Issues: Open an issue if you find a bug or have a suggestion
• Participate in Discussions: Join the conversation on our GitHub Discussions. Review RFCs, share ideas, and help shape the future of the project.
• Contribute Code: Check out our Contributing Guidelines

License

MIT © javierbrea