Wrdn Package Boundaries

Preserve workspace package boundaries. Use when lint flags relative imports that cross package roots.

usefulsoftwareco 34dfdc9 731 B Updated

File contents

Workspace packages should import each other through package exports, not relative paths.

Fix Shape

  • Replace cross-package relative imports with the target package name.
  • If the needed module is not exported, add the smallest package export that matches the package's public surface.
  • Keep relative imports only within the same package root.
  • Do not reach into another package's private source tree from an app or package.

Good

import { createExecutor } from "@executor-js/sdk";

Bad

import { createExecutor } from "../../../core/sdk/src";

usefulsoftwareco/executor/tree/main/.agents/skills/wrdn-package-boundaries commit 34dfdc92f2

Frequently asked questions

npx skillmds@latest add usefulsoftwareco/wrdn-package-boundaries