How john-smilga/mern-jobify-v2 works
Project Type and Purpose
• This is a full-stack “Jobify” application:
• Front-end SPA built with Vite + React + React Router + React Query + Styled-Components + Recharts.
• Back-end REST API built with Node.js + Express, MongoDB (via Mongoose), JWT authentication, file uploads to Cloudinary.
File Structure for Architectural Layers
• client/ → React application (pages, components, assets, utils).
• server.js, routes/, controllers/, models/, middleware/, utils/ → Express API.
• populate.js for initial data seeding; utils/mockData.json for test jobs.
• Configuration files: .env, package.json, vite.config.js, .gitignore.
Main Components & Responsibilities
a. Front-end Client
• React Router layout/pages: Landing, Register/Login, Dashboard (nested routes: AddJob, AllJobs, Stats, Profile, Admin).
• React Query for data fetching & caching.
• Axios/customFetch wrapper for HTTP calls to /api/v1/*.
• UI components (FormRow, Job, JobInfo, ChartsContainer, StatsContainer, PageBtnContainer, etc.).
b. Express API
• Middleware chain: helmet, express-mongo-sanitize, rate-limiter, cookie-parser, multer (file parsing), authMiddleware (JWT), validationMiddleware, errorHandlerMiddleware.
• Routers: authRouter (/api/v1/auth), jobRouter (/api/v1/jobs), userRouter (/api/v1/users).
• Controllers: handle CRUD, auth, stats, file upload logic (Cloudinary).
• Mongoose models: UserModel, JobModel.
c. Data Stores & External Services
• MongoDB Atlas (jobs & users collections).
• Cloudinary (user avatars).
• Local file buffer via Multer + DataURI → Cloudinary upload.
• HttpOnly cookies for JWT.
Relationships & Data Flows
• Browser → React SPA → HTTP(S) (via Axios/customFetch, proxied in dev by Vite) → Express API.
• Express parses JWT from HttpOnly cookie → authMiddleware → controllers.
• Controllers interact with Mongoose to read/write MongoDB.
• Profile updates: Multer parses file → DataURI → Cloudinary API → returns URL → saved in User document.
• Controllers return JSON → React Query updates cache & UI.
• React Router loaders/actions drive data fetching & mutations (formData → API calls → redirects/toasts).
Architectural Patterns & Principles
• Front-end: SPA with route-based code organization, loader/action pattern, server-state management via React Query.
• Back-end: RESTful MVC-style layering: middleware → router → controller → model.
• Stateless authentication (JWT in cookie).
• Modular error handling (custom error classes + express-async-errors).
• Security hardening: helmet, express-mongo-sanitize, express-rate-limit.