DevTools import boundaries

DevTools import boundaries

Every @devtools/* package is self-contained. The only permitted cross-package imports within the devtools scope are listed in the table below; all others are forbidden.

Rules

All other @devtools/* → @devtools/* imports are forbidden.

Why

The devtools architecture decouples tools from the shell through the registry. The shell lazy-loads tools via metadata.loader; tools never know the shell exists. If a tool imports the shell or another tool directly:

• The lazy-load boundary collapses — the tool is bundled eagerly.
• A circular dependency becomes likely (tool → shell → registry → tool).
• The tool can no longer be rendered standalone, outside the shell.

If bindings or shell import a tool package directly (instead of through the registry):

• The registry's discriminated union is bypassed and TypeScript loses the narrowing guarantee on DevToolsConfig.
• The import() split point disappears, defeating code-splitting.

Consequences of a violation

• Tool imports shell or registry: The tool becomes coupled to shell internals; standalone rendering and unit-testing break.
• Tool imports another tool: Cross-tool coupling; removing or renaming one tool requires editing the other.
• Shell or bindings import a tool directly: Eager bundle; code-split lost; registry union integrity broken.

Correct pattern