typescript-circular-dependency

TypeScript compiles cleanly but throws a runtime initialization error because circular import dependencies create initialization loops where modules reference each other before fully loading. This Skill detects these import cycles and recommends extracting shared types or using type-only imports to resolve the undefined exports.

To fix circular import dependencies in a JavaScript codebase, this Skill analyzes the import loops and proposes the smallest safe refactor, such as switching to type-only imports, applying dependency injection, or replacing barrel-file imports with direct paths to eliminate the runtime failures.

Flaky test behavior with 'Cannot access before initialization' in services is caused by circular import dependencies that disrupt module loading order. This Skill traces the import loops in your components and shared types, providing resolution guidance to restructure the modules safely.

To prevent circular dependencies from returning in a TypeScript project, this Skill demonstrates how to add cycle checks to your CI pipelines and linting workflows, ensuring that import loops and barrel-file import issues are caught before they cause runtime errors.

Yes, this approach works for resolving barrel-file import loops in shared types by analyzing the module resolution paths, identifying the specific cycles causing flaky test behavior, and recommending direct path imports or type-only imports to break the dependency loops.