Skip to main content

Framework-Specific Guides

Using ARCLUX with your specific framework? Here’s what to look for!

Next.js Projects

What ARCLUX Checks for Next.js

When you run:
ARCLUX checks:
  1. App Router structure (pages in /app)
  2. API routes (must be in /app/api)
  3. Layout organization
  4. Component placement

Expected Output Example

Common Issues & Fixes

Issue: β€œRoute /old-page β†’ NO CORRESPONDING FILE FOUND”
  • Meaning: You have a route defined but no actual file
  • Fix: Create the missing page.tsx OR remove the reference
Issue: β€œComponent imports server-only lib in client component”
  • Meaning: Using server-only code in client component
  • Fix: Add "use client" directive at top of file

Tips for Next.js


NestJS Projects

What ARCLUX Checks for NestJS

ARCLUX verifies:
  1. Module organization
  2. Service dependencies
  3. Controller structure
  4. Circular dependencies (major issue!)

Expected Structure

Common Issues & Fixes

Issue: β€œCircular dependency in NestJS modules”
  • Meaning: Module A imports Module B, and vice versa
  • Fix: Refactor to extract shared logic to third module
Issue: β€œService imported directly instead of via Module”
  • Meaning: Breaking NestJS dependency injection pattern
  • Fix: Import via Module, not direct service

Tips for NestJS


Express Projects

What ARCLUX Checks for Express

ARCLUX verifies:
  1. Route organization
  2. Middleware structure
  3. Controller isolation
  4. Service layer separation

Expected Structure

Common Issues & Fixes

Issue: β€œController imports from routes”
  • Meaning: Breaking layer separation
  • Fix: Routes import controllers, not vice versa
Issue: β€œBusiness logic in routes”
  • Meaning: Not using controller/service pattern
  • Fix: Move logic to service, call from controller

Tips for Express


React Projects

What ARCLUX Checks for React

ARCLUX verifies:
  1. Component structure
  2. Hook organization
  3. State management patterns
  4. Dead components

Expected Structure

Common Issues & Fixes

Issue: β€œComponent never imported anywhere”
  • Meaning: Orphan component
  • Fix: Delete or find use for it
Issue: β€œHook used in multiple places”
  • Meaning: Good! Reusable logic
  • Keep: This is the pattern to follow

Tips for React


TypeScript Projects

What ARCLUX Checks for TypeScript

ARCLUX verifies:
  1. Type imports vs value imports
  2. Module boundaries
  3. Interface usage
  4. Type organization

Expected Structure

Common Issues & Fixes

Issue: β€œType imported as value”
  • Meaning: Using import { Type } instead of import type { Type }
  • Fix: Use import type for types only
Issue: β€œCircular type dependencies”
  • Meaning: Type A references Type B, Type B references Type A
  • Fix: Refactor to extract common types

Tips for TypeScript


Multi-Language Projects

Using ARCLUX with Multiple Languages

ARCLUX supports:
  • TypeScript
  • JavaScript
  • Python
  • Go
  • Java

How to Use

Example: Mixed TS + Python Project

Output:

Tips for Multi-Language Projects


Monorepo Projects

Using ARCLUX with Monorepos

ARCLUX works great with monorepos:

Typical Monorepo Structure

Benefits for Monorepos

  1. See cross-package dependencies
  2. Check for circular imports between packages
  3. Understand impact of changes

Don’t See Your Framework?

ARCLUX works with any TypeScript/JavaScript project! The guides above are just recommendations. You can still:
  • βœ… Run analyze
  • βœ… Find circular dependencies
  • βœ… Check impact analysis
  • βœ… Find dead code
It all works! Try it out!
Pick your framework above and get started! πŸŽ‰