reversa-docs-mapper

To generate 3D and 2D architecture visualizations, you map extracted modules and dependencies into navigable maps. This produces a Three.js Code City for spatial layout and a D3 force-directed graph for exploring module edges and dependency cycles.

Mapping dependency cycles is best achieved by generating a 2D force-directed module graph with D3. This visualization renders nodes and edges, letting you visually explore and identify circular dependencies within your system architecture.

To generate documentation pages from modules.json and deps.json, you inject the extracted data via window.RV_DATA into a viewer.html chassis. The pipeline then writes the rendered architecture and module pages into a .reversa/documentation directory.

Yes, you can generate side-by-side topology visualizations comparing legacy, modern, and hybrid architectures. When topology is detected in the system definition, the pipeline automatically produces a comparative topology page alongside the standard architecture maps.

Caching reuses valid JSON files stored in assets data when generating visualizations. The pipeline only re-extracts modules and dependencies when the cached files are invalid or missing, ensuring efficient reuse of intermediate architecture artifacts.

You do not need Three.js or D3 installed locally to render Code City and force-directed graphs. The pipeline injects data via window.RV_DATA into a viewer.html chassis with correct head extras, handling rendering without local fetch dependencies.