Hackmate Cli

Core System Architecture

The application is structured around a central api.ts module that configures an axios client with a dynamic base URL (getApiUrl) and attaches the authentication token (getToken) to every request via request interceptors. Response interceptors emit an unauthorized event on 401 responses, allowing the CLI to react globally to session expiration.

Data Flow & Execution:

• UI components (React hooks such as useAsyncRequest, useAdminLogic, useNetwork) invoke service methods.
• Service methods (AuthService, UserService, ChatService, etc.) perform HTTP calls to well‑defined REST endpoints and return typed promises.
• Hook utilities manage loading, error, and authentication state, ensuring that unauthenticated users receive a clear prompt ("Please login first using \"hackmate auth login\"").

Security Guardrails

Authentication tokens are stored via the config utilities and injected into request headers as Authorization: Bearer <token>. The interceptor pattern centralizes token handling and unauthorized detection, reducing duplicated error handling across services.

Build & Distribution

Source files are written in TypeScript and compiled to JavaScript in the dist/ directory. The project includes a .gitignore that excludes node_modules, build artifacts, environment files, and user configuration (config.json). The CLI entry point (cli.tsx) likely uses a bundler to produce an executable script, while the scripts/add-shebang.cjs helper ensures the generated binary is directly runnable.

Extensibility

Each domain service is isolated, making it straightforward to add new endpoints or replace the underlying HTTP client. Hook abstractions (useAsyncRequest) provide a reusable pattern for future feature development, promoting consistency across the codebase.