How team-zero-dsm/greener works
GreenER is currently a development scaffold rather than a documented domain product: its frontend renders a placeholder screen, and its backend exposes a health endpoint. The graph shows those runtime paths only. The README and sampled source do not establish a connection between frontend and backend or describe the database’s role, so neither is inferred.
Main entry points: main.tsx React Mount · App.tsx Placeholder Screen · app.ts Health API · server.ts HTTP Server
Components 8
Frontend
- React Mount
frontend/src/main.tsx - Placeholder Screen
frontend/src/App.tsx - Card Components
frontend/src/components/ui/card.tsx
Backend
- HTTP Server
backend/src/server.ts - Health API
backend/src/app.ts
Other components
- Visitor
- Browser
- Health Checker
Connections 6
- Visitor → Browser: uses
- Browser → React Mount: loads
- React Mount → Placeholder Screen: renders
frontend/src/main.tsx - Placeholder Screen → Card Components: renders
frontend/src/App.tsx - HTTP Server → Health API: serves
backend/src/server.ts - Health Checker → Health API: requests health
backend/src/app.ts