How nithish699/fullstack_universiyofhelsinki works
• A high-level overview showing each Part as a module,
• Or focus on the full-stack Part 3 as the flagship exercise.
Project Type & Purpose
• It’s a learning submission repository containing:
• Part 0: notes and markdown pages (static content)
• Part 1: three pure React single-page apps (Anecdotes, Courseinfo, Unicafe) built with Vite
• Part 2: three React apps that call external services (Countries API, Course API, JSON-server Phonebook)
• Part 3: a full-stack phonebook—React front-end + Node/Express backend exposing REST endpoints, backed by a simple JSON file.
File Structure
• Top-level directories: Part0, Part1, Part2, Part3
• React apps share a pattern:
frontend asset root (index.html, public/) → src/ (main.jsx, App.jsx, components/) → package.json + Vite config
• Services layer in Part 2/phonebook: src/services/persons.js makes HTTP calls to a JSON-server
• Part 3/phonebook:
• index.js sets up Express routes
• requests/*.rest are sample HTTP calls (for testing with REST Client)
• No build pipeline—Node app runs directly under node index.js
Extract README Insights
• Confirms this is a full-stack course submission.
• Technologies: React, Vite, Node.js, Express, ESLint.
a. Main Components
• For each React app:
• Browser / User
• Vite Dev Server (local dev) / Build Pipeline (prod)
• React UI Components (App.jsx, subcomponents)
• Static Assets (public folder, CSS)
• For Part 2 that uses APIs:
• Service Modules (services/*.js)
• External APIs (e.g., REST Countries, OpenWeather)
• For Part 3 full-stack:
• Frontend (React + Vite)
• HTTP Client (axios or fetch calls)
• Express Backend (Node.js, index.js)
• Data Store (JSON file or in-memory array)
• REST Endpoints (GET /api/persons, POST, DELETE, etc.)
b. Relationships & Interactions
• User interactions flow into the browser → React UI → service modules → API calls
• For full-stack: React → HTTP → Express routes → Data store → Express → React
c. Architectural Patterns
• Component-based UI (React)
• Separation of Concerns: UI vs. data-access (services folder) vs. server logic
• RESTful API in Part 3
d. Key Technologies
• React + JSX, Vite, ESLint
• axios or fetch in services
• Node.js, Express for backend
• JSON file storage (or JSON-server in Part 2)
• Optional: REST Client tool (.rest files)