boundary-checker

To check FSD import boundary violations in a TypeScript codebase, analyze your source files against a layer map to detect cross-layer and cross-slice imports. This surfaces structural violations across your layered architecture.

FSD cross-slice imports occur when one slice within the same layer directly imports from another, breaking layered architecture isolation. Detecting these violations ensures slices remain independent and maintain proper public API boundaries.

To validate @x/ cross-references in Feature-Sliced Design, apply optional cross-reference rules during import analysis to ensure higher-layer slices only access lower-layer slices through designated public APIs, preventing improper internal path imports.

Yes, you can enforce public API usage rules across app, pages, widgets, features, and entities layers by evaluating TypeScript imports against your defined layer map and flagging internal path accesses that bypass public APIs.

To start analyzing FSD layer hierarchy violations, you need to provide the root path to your codebase for file content access and a defined layer map specifying your rules for extracting and evaluating TypeScript imports.

Generate a report of higher-layer import violations by scanning all source files and extracting imports that breach the layer hierarchy. This structured output guides targeted refactoring and codebase cleanup efforts.