How praveenvarshney619/code-forge-online-compiler- works
Project Type & Purpose
• Full-stack online IDE / collaborative code editor
• Frontend built in Next.js + Tailwind CSS
• Backend in Node.js + Express.js, exposing REST endpoints for compile/scrape and a WebSocket channel for real-time collaboration
Main Components
A. Frontend (Next.js App)
– UI Layer: editor, language selector, input/output panes (components/FileEditor.jsx, LanguageDropdown.jsx, Output.jsx, etc.)
– Theme and styling (Tailwind + defineTheme.jsx)
– Data/API layer (frontend/services/index.js) for REST calls and WebSocket client
– Static assets (public/images, styles/globals.css)
B. Backend (Express Server)
1. REST API Controllers
• compileControllers.js – writes temp files, invokes system compiler (g++, javac, python), returns stdout/stderr
• scraperController.js – fetches coding problems via HTTP from external sites, parses HTML, returns JSON
2. WebSocket Controller
• socketController.js – socket.io (or ws) server to broadcast editor state changes between clients
3. Temp & Output Storage
• /temp – holds incoming code files and input.txt for each compile request
• /output – stores generated executables and console output
4. Server Entry Point
• server.js – mounts REST routes, initializes WebSocket server
C. External Services
– Code compilation toolchain (system g++, javac, python interpreters)
– Third-party websites for scraping coding questions
– (Optional) Logging/Monitoring, if present
Relationships & Data Flows
• User edits code → Frontend WebSocket client emits “code-update” → Backend socketController broadcasts to peers
• User clicks “Run” → Frontend sends POST /compile → compileController writes to /temp, runs compiler, reads /output, responds JSON → Frontend displays output
• User requests a problem → Frontend GET /scrape → scraperController fetches & parses external site, returns problem data → Frontend populates editor/description
Architectural Patterns & Principles
– Layered Architecture: UI Layer → API Layer (REST + WebSocket) → Business Logic Layer (compilation, scraping) → System Calls & File I/O
– MVC-style grouping in backend (controllers)
– Separation of concerns: collaboration sync (WebSocket) vs. one-off operations (REST)
– Stateless services: REST endpoints are idempotent aside from file I/O in temp/output