How tcc-refactor/refactor works
ReFactor is a minimal Angular application shell, not a domain workflow: the README documents setup and running the app but no product-specific capabilities. Its runtime flow is browser bootstrap into the root component, with an Express/Angular SSR path for server requests; server routes are configured for prerendering. The graph reflects only the sampled entry points and configuration. The template and styling files are present in the tree but were not sampled, so their behavior is not inferred.
Main entry points: main.ts Client bootstrap · app.config.server.ts SSR configuration · app.config.ts App configuration · main.server.ts Server bootstrap
Components 10
Client application
- Client bootstrap
src/main.ts - App configuration
src/app/app.config.ts - Client routes
src/app/app.routes.ts - Root app
src/app/app.ts
Server rendering
- Server bootstrap
src/main.server.ts - SSR configuration
src/app/app.config.server.ts - Prerender routes
src/app/app.routes.server.ts
HTTP serving
- Express server
src/server.ts - Angular SSR engine
Other components
- Browser user
Connections 9
- Browser user → Client bootstrap: opens app
README.md - Client bootstrap → App configuration: bootstraps with
src/main.ts - Client bootstrap → Root app: bootstraps
src/main.ts - App configuration → Client routes: provides router
src/app/app.config.ts - Server bootstrap → Root app: bootstraps
src/main.server.ts - Server bootstrap → SSR configuration: bootstraps with
src/main.server.ts - SSR configuration → App configuration: merges config
src/app/app.config.server.ts - SSR configuration → Prerender routes: configures rendering
src/app/app.config.server.ts - Express server → Angular SSR engine: handles requests
src/server.ts