CareSync Repository Architecture: Frontend SPA + Backend API Surface

Overview

Frontend: Vite-powered Single-Page Application (SPA)
Backend API Surface: HTTP endpoints exposed under /api
Repository Structure Goal: Keep shared domain types and a strongly-typed client in src/

Runtime Modes (Vite)

if (process.env.NODE_ENV !== 'production') {
  console.log('[CareSync] Running in development mode with Vite middleware...');
  const vite = await createViteServer({
    server: { middlewareMode: true },
    appType: 'spa',
  });

  app.use(vite.middlewares);
} else {
  console.log('[CareSync] Running in production mode...');
  const distPath = path.join(process.cwd(), 'dist');
  app.use(express.static(distPath));

  // SPA fallback
  app.get('*', (req, res) => {
    // serve index.html
  });
}

API Client Contract

CareSync uses a strongly-typed client to centralize request logic and ensure consistent API usage.

File: /src/lib/api.ts

/**
 * Strongly-typed API client for CareSync
 */

const API_BASE = '/api';

export class APIClient {
  private static getToken(): string | null {
    return localStorage.getItem('caresync_token') || 'user-123'; // Seed fallback
  }

  static async explainMedicine(name: string, dosage: string, notes: string): Promise<any> {
    return this.request<any>('/ai/explain', {
      method: 'POST',
      body: JSON.stringify({ name, dosage, notes })
    });
  }
}

Shared Types

File: /src/types/index.ts

User model includes settings: UserSettings
Shared types support consistent frontend/backend contracts

Architecture Diagram (Conceptual)

CareSync.git

→

Vite SPA (src/)

→

Backend API Surface

Request Flow

APIClient targets API_BASE = '/api'
Example: POST /api/ai/explain (from explainMedicine())
Token retrieved from localStorage (fallback seed: user-123)

Key takeaway: the repository cleanly separates a Vite SPA frontend from a versioned API surface under /api, with shared TypeScript types and a strongly-typed client.