Reading about Node.js only goes so far — the concepts in this notebook click into place once you've actually hit the problems they solve. Below are project ideas grouped by difficulty, each with enough of a description to start building without a step-by-step tutorial.
Beginner — solidifying the fundamentals
- Command-line to-do list — store tasks in a JSON file with
fs, and build add/complete/delete commands read fromprocess.argv. Exercises the file system module and basic CLI argument handling. - URL shortener — an Express app storing short-code-to-URL mappings, with a redirect route. A clean first project for routing and a simple data store.
- Markdown-to-HTML converter — read a
.mdfile, convert it, write the result out. Good practice with streams if you process large files chunk by chunk instead of all at once. - Weather CLI tool — take a city name as a command-line argument, call a public weather API with
httpsoraxios, print the result. First real exposure to making outgoing HTTP requests and handling async responses. - Simple contact book API — CRUD routes (Create, Read, Update, Delete) backed by a JSON file or an in-memory array. The classic starting point for understanding REST conventions.
Intermediate — combining several concepts
- Blog API with authentication — Express routes for posts, plus JWT-based login so only authenticated users can create or edit posts. Combines routing, middleware, and
crypto/jsonwebtoken. - Real-time chat app — a WebSocket-based server (via the
wspackage or Socket.IO) broadcasting messages to connected clients instantly. A strong, hands-on introduction to persistent connections and event-driven communication. - File upload and image resizing service — accept an uploaded file (via
multer), process it with an image library, save both original and resized versions. Touches streams, buffers, and the file system together. - Task queue with a worker process — a main server that hands heavy jobs (like sending bulk emails) to a
child_processfork, keeping the main thread responsive. Direct, practical use of everything covered in the Child Process page. - Rate-limited public API — track request counts per IP in memory or Redis, rejecting requests past a threshold. Good practice with middleware and basic state management.
Advanced — production-shaped problems
- Video/audio streaming server — serve large media files using
fs.createReadStream()with properRangeheader support, so a video player can seek without downloading the whole file first. - Multiplayer game server — real-time state synchronization across connected clients using WebSockets, with server-authoritative logic to prevent cheating.
- A small microservices setup — split a single app into two or three independent Node.js services (say, an auth service and a data service) that communicate over HTTP or a message queue, deployed and run separately.
- Log aggregation tool — a service that receives logs from multiple sources over UDP or HTTP, processes and compresses them with
zlib, and writes them to rotating files. - A CLI tool published to npm — build something genuinely useful, package it properly (following the steps on the Creating and Publishing NPM Packages page), and publish it for others to install.
A note on how to actually use this list
Picking a project slightly above your current comfort level, and actually finishing it — including the unglamorous parts like error handling and edge cases — teaches far more than reading through five different tutorials on the same topic. When you get stuck, that's usually the exact moment worth returning to the relevant chapter in this notebook rather than searching for a ready-made answer; understanding why the fix works is what actually sticks.