TypeScript project · Generated dependency data
Vue Core Architecture Report
Vue Core contributes a Dependency Cruiser file covering 12 production source roots, 731 modules, and 1,951 dependencies. AtlasArc reports its source folders in Architecture Overview, Cycle Evidence, Hotspot Risk, and a capped Evidence Appendix.
- Source folders
- 31
- Dependency edges
- 94
- Cycle groups
- 8
- Chapters
- 4
- Report date
- 31 Jul 2026
Why we included this report
We chose Vue Core because its generated dependency data covers 12 production source roots. AtlasArc reports 31 source folders instead of JVM packages.
That model produces Architecture Overview, Cycle Evidence, and Hotspot Risk over 94 folder-to-folder edges and eight cycle groups. The source-folder unit remains visible throughout those chapters.
Selected evidence
- Global architecture model
- Architecture Overview, Cycle Evidence, and Hotspot Risk
- One diagram for each cycle group, with an extra view only when it adds relationships not already shown
- Short diagnostic lists that explain why each source folder or dependency was selected
- Evidence Appendix with at most 50 rows in each detailed register
Choose what you want to understand
If this is your first Architecture Report, start with Architecture Overview for the big picture. Then choose the question you care about; each description explains what that chapter will help you understand. Each link opens the chapter in the full report.
- 01 Architecture OverviewStart here to see how Vue Core's source folders are organized, which folders depend on one another, and where its eight dependency loops appear in the whole-project map.
-
02
Cycle EvidenceSee all eight source-folder dependency loops together, then trace the relationships that keep each loop closed.
To compare this TypeScript project with a Kotlin/JVM project, open Detekt's chapter. Compare Detekt’s Cycle Evidence
- 03 Hotspot RiskFind source folders where changes may spread widely, then see whether the pressure comes from incoming dependencies, exposed code, or tightly connected internals.
- 04 Evidence AppendixUse the capped source-folder and dependency registers when a deeper review or handoff needs more literal evidence than the short diagnostic lists.
What this report covers
- Source revision
- b5f8518379b77c3b62a7a9d2b52f6c76cda09bd5
- Licence
- MIT
- Language and evidence
- TypeScript · artifact-backed Dependency Cruiser data generated by the project
- Project scale
- 12 production source roots · 731 modules · 1,951 dependencies
- Report contents
- Whole project + Cycle Evidence + Hotspot Risk + detailed evidence appendix
- Report date
- 31 July 2026
- AtlasArc version
- 1.0.0
How to use this case
Context here, evidence in the report
Use this page to understand the project snapshot and scope. Open the report to inspect the architecture chapters themselves.
View project sourceHow this example was prepared
-
Use the recorded source revision
Check out the Vue Core revision linked on this page.
-
Build the project
Install, build, and verify the project with the Node and pnpm versions shown above.
-
Generate the dependency data
Run Dependency Cruiser 17.4.3 over the 12 production source roots with TypeScript 5.6.3.
-
Choose the report chapters
Import the generated dependency data and include Architecture Overview, Cycle Evidence, Hotspot Risk, and detailed evidence tables with a 50-row maximum.
Source and attribution
Open-source project. Pinned example.
Vue Core is analyzed from the pinned source revision above under MIT . The project name identifies the analyzed open-source snapshot; publication here does not imply affiliation with or endorsement by its maintainers.