Case Study
Architecture Case Study: Next.js (packages/next)
Full capability workflow on Next.js (packages/next)
Project: Next.js (packages/next)Score: 89/100 (A)1,942 modules4,489 edges
Architecture visualization
Diagrams are generated from ArcSight analysis data. Dependency graph and risk map show key modules; subsystem view shows high-level structure.
Architecture score & metrics
Score: 89/100
Critical findings
src/shared/lib/app-router-typesCRITICALfan-in: 45src/server/lib/lru-cacheHIGHfan-in: 12src/shared/lib/segmentHIGHfan-in: 23
Hotspots
src/typesCRITICALfan-in: 21blast: 423src/server/config-sharedCRITICALfan-in: 46blast: 423
Dependency corridors
Repeated paths where changes propagate through the same modules.
- src/server/config-shared → src/server/request-meta → src/server/request/params
- src/types → src/shared/lib/utils → src/server/app-render
Subsystem overview
- next-next-devtools(120 modules)
- client-app-call-server(85 modules)
Architectural gravity centers
src/types— shared utility hubsrc/server/config-shared— central orchestrator
CLI workflow
Scan → Fix → Finish → Watch. Nothing else required.
arc scanFind issuesarc fixApply fixesarc finishResolve remainingarc watchKeep clean (Pro)
Key takeaways
- •Architecture score 89/100 indicates a healthy structure with room to reduce cycles and violations.
- •High fan-in modules are change-risk zones; run
arc explain <path>before refactoring. - •Run the full workflow (analyze, hotspots, explain, impact, snapshot, drift) in your repo for deterministic architecture insights.
Run ArcSight on your repo
Install the CLI and run analyze, then hotspots and explain for the same workflow.
This case study is generated from ArcSight analysis data. View short analysis. View all analyses