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:- App Router structure (pages in
/app) - API routes (must be in
/app/api) - Layout organization
- 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
- 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:- Module organization
- Service dependencies
- Controller structure
- 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
- 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:- Route organization
- Middleware structure
- Controller isolation
- Service layer separation
Expected Structure
Common Issues & Fixes
Issue: βController imports from routesβ- Meaning: Breaking layer separation
- Fix: Routes import controllers, not vice versa
- 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:- Component structure
- Hook organization
- State management patterns
- Dead components
Expected Structure
Common Issues & Fixes
Issue: βComponent never imported anywhereβ- Meaning: Orphan component
- Fix: Delete or find use for it
- Meaning: Good! Reusable logic
- Keep: This is the pattern to follow
Tips for React
TypeScript Projects
What ARCLUX Checks for TypeScript
ARCLUX verifies:- Type imports vs value imports
- Module boundaries
- Interface usage
- Type organization
Expected Structure
Common Issues & Fixes
Issue: βType imported as valueβ- Meaning: Using
import { Type }instead ofimport type { Type } - Fix: Use
import typefor types only
- 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
Tips for Multi-Language Projects
Monorepo Projects
Using ARCLUX with Monorepos
ARCLUX works great with monorepos:Typical Monorepo Structure
Benefits for Monorepos
-
See cross-package dependencies
-
Check for circular imports between packages
-
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
Pick your framework above and get started! π