How deepraj21/buildlab works
Project type and purpose
• BuildLab is a full-stack hybrid web/mobile application.
• Purpose: Let users query an AI to scaffold, run, and edit React projects in a browser-embedded IDE and terminal; support AI-powered search, group chat, and private “spaces.”
File structure
• Top-level separation:
• app/client → the frontend (web + mobile via Capacitor/Android)
• app/server → the backend (Node.js/Express controllers, services, models)
• client/src → React+TypeScript (Vite) with pages, components, routes, UI library, config (axios, socket).
• client/android → Capacitor Android wrapper (native Android project + Java MainActivity).
• server/
• controllers → HTTP handlers by domain (ai, chat, project, blog, user)
• services → business logic (ai.service calls LLMs & Google, project.service scaffolds code, redis.service for caching, user.service, etc.)
• models → data schemas (blog, project, user)
• middleware → auth checks
• routes → Express routers wired to controllers
• server.js/app.js → Express app entrypoints
Readme insights
• Tech stack: React+TSX (Vite), Tailwind CSS, ShadCN UI, Capacitor for Android, Node.js backend.
• Features: AI-powered search, React project generation agent, chat (@ai and group), private workspaces (“spaces”), in-app browser/terminal.
• External integrations: OpenAI or other LLMs, Google search scraping, Postman-documented REST API.
Detail
• Sub-module (ai.controller vs. chat.controller vs. project.controller).
• Middleware (auth) as a separate stage in the request flow.
• In-app browser/terminal module hosting generated React projects.
• Real-time channels (Socket.IO) vs. standard REST.