How mariocodev/ng-dragon-ball-api works
Project Type and Purpose
• This is an Angular-based web application (with optional server-side rendering via Express).
• It serves as a responsive SPA that consumes the external Dragon Ball API to list and filter characters, and display details in a modal.
• Key features: reactive filters, dark/light theme toggling, SSR entry point (server.ts + main.server.ts), and proxy configuration for API calls in development.
File Structure Analysis
• Top level
• angular.json, package.json / package-lock.json → Angular CLI configuration and dependencies.
• server.ts, src/main.server.ts → Express server bootstrap + Angular Universal SSR.
• proxy.config*.json → Local API proxy for development.
• public/ → Static assets served by Express.
• src/
• src/main.ts → Browser app entry point.
• src/app/
– app.component.*, app.routes.ts → Root component and client routing.
– app.config.ts / app.config.server.ts → Environment-specific configuration.
– pages/character-details → Feature component for character detail view.
– shared/models → Data interfaces for API responses.
– shared/services/dragon-ball.service.ts → HTTP client for remote API.
• Tailwind + Flowbite styling via tailwind.config.js and global styles.scss.
• Environment files under src/environments for dev/prod builds.
README Insights
• Frontend tech stack: Angular 18, Tailwind CSS + Flowbite, npm.
• Dev flow: nvm → Node.js → Angular CLI → npm scripts for start:uat, build:dev/uat/prod.
• Environments: dev, uat (staging), prod.
• Emphasis on proxy usage and environment flags.
Components
a. Client Tier
• Browser (User Interface)
• Angular SPA (app shell + client-side routing)
• Reactive Forms module for filters
• Theme toggler
b. Server Tier (optional SSR)
• Express server (server.ts)
• Angular Universal (main.server.ts)
• Static asset handler (public/)
c. External Services
• Dragon Ball API (https://web.dragonball-api.com)
• Proxy layer (/api → remote) for CORS during dev
d. Build & Deployment
• npm scripts (start:uat, build:prod, etc.)
• Environment configurations (src/environments/*.ts)
• TailwindCSS pipeline
Relationships & Interactions
• Browser → Express (SSR) on initial page load → Angular Universal renders HTML.
• Browser (hydrated Angular) → DragonBallService → HTTP GET /api/… → Proxy → Dragon Ball API → JSON Response → UI.
• User filters input → Reactive Forms → DragonBallService calls → UI update.
• Environment flags toggle API endpoints and production optimizations.
Architectural Patterns & Principles
• SPA with optional SSR (Universal) for SEO / performance
• Modular feature segregation (pages vs. shared)
• Service-based API access (single responsibility)
• Environment-driven builds (dev/uat/prod)
• Utility-first CSS (Tailwind + Flowbite)
Detailed Breakdown to Capture
• App Shell: app.component, routing module
• Feature Module: CharacterDetailsComponent
• Shared Layer: Models + DragonBallService
• Environment Configurator: app.config.ts vs. app.config.server.ts
• Build Pipeline: npm run build:dev/uat/prod → output hashing
• Deployment Targets: dev / uat / prod servers serving static assets or SSR
• Styling Engine: TailwindCSS + Flowbite