Get Programming with Node.js (Jonathan Wexler)（Z-Library）

# Get Programming with Node.js — Reading Guide ## 【One-Line Pitch】 A hands-on, project-driven introduction to building web servers and full web applications with Node.js, perfect for JavaScript developers who want to move from writing scripts to deploying real-world apps. If you learn best by typing code and watching it work, this book will take you from your first server to a production-ready chat application. --- ## 【Book Arc】 - **Opening (~0%–10%)**: Sets up the entire learning environment — installing Node.js, choosing a text editor, configuring Git and Heroku, and running your first JavaScript file. The author emphasizes typing every example yourself rather than copying and pasting, and introduces the REPL for experimenting with code interactively. - **Early (~10%–25%)**: Covers Node.js fundamentals — modules, packages, dependencies, and npm commands — then builds your first simple web server using only core Node.js modules. You learn the request-response cycle and how to handle basic routing with plain JavaScript before any frameworks are introduced. - **Early (~25%–35%)**: Expands your server to serve complete HTML files, static assets (CSS, images, client-side JavaScript), and introduces the `fs` module for file operations. You also refactor routes into their own module for cleaner organization — your first step toward professional project structure. - **Middle (~35%–50%)**: Introduces Express.js as a web framework that dramatically simplifies routing, middleware, and request handling. You install nodemon for auto-restarting during development, learn to parse request bodies and query strings, and set up configuration variables and error handling with Express. - **Late (~50%–100%)**: The capstone project — Confetti Cuisine, a cooking-class website — ties everything together. Users can sign up, connect, and chat about recipes, which means implementing user authentication, database management, and deploying to production on Heroku. The excerpts confirm the book's structure but don't detail these final lessons. --- ## 【Key Takeaways】 - **Type every example yourself** (Early): The author is explicit — copying and pasting code leads to errors and prevents learning. The "three times" method (follow the guide, use the guide as reference, then work alone) builds genuine understanding. - **Modules, packages, and dependencies are distinct concepts** (Early): Modules are single JavaScript files for one purpose; packages group related modules; dependencies are modules your app requires to run. Understanding this vocabulary prevents confusion throughout the book. - **npm flags control where packages live** (Early): `--save` (or `-S`) installs production dependencies, `--save-dev` for development-only tools, and `--global` (or `-g`) for command-line utilities. This distinction matters when you deploy to production. - **The request-response cycle is the foundation of web servers** (Early): A client sends an HTTP request, the server processes it, and returns a response — HTML, JSON, or plain text. Every web interaction, from Google searches to your own apps, follows this pattern. - **Core Node.js can serve files without frameworks** (Early): Using the `fs` module and `http` module, you can serve HTML files, handle missing files with 404 responses, and organize routes into separate modules — all before touching Express. - **Express.js simplifies but doesn't replace understanding** (Middle): Express handles routing, middleware, and request parsing (like reading POST bodies) with less code, but the underlying concepts from earlier lessons — routes, callbacks, error handling — remain essential. - **nodemon eliminates manual server restarts** (Middle): Install it globally or as a devDependency, and it automatically restarts your server when files change. Configure it via the `start` script in `package.json`. - **Configuration and error handling are production concerns** (Middle): Use `app.set` for reusable settings like port numbers (with `process.env.PORT` fallback), and create dedicated error controllers with proper HTTP status codes rather than letting Express show unfriendly `Cannot GET /` messages. --- ## 【Reading Tips】 - **Skim Unit 0 if you're experienced**: The setup lessons (installing Node, Git, Heroku) are straightforward. But don't skip Lesson 2 — running your first application and using the REPL builds muscle memory. - **Deep-read Lessons 3–6**: These cover modules, npm, and building a server from scratch with core Node.js. This is where you learn what Express actually does for you later — the foundation is worth the effort. - **Watch for the "Quick check" answers**: They're embedded in the text (like the callback function answer in Lesson 5). These are mini-quizzes that confirm you understand key concepts before moving on. - **Do the capstone project twice**: The author recommends redoing the Confetti Cuisine project after your first pass. The first time you follow along; the second time you build independently — this is where the learning sticks. - **Windows users: install Git Bash**: The book teaches from a UNIX perspective, and Git Bash gives Windows users the same terminal commands without translation issues. --- ## 【Coverage Limits】 This guide covers the book's structure and early-to-middle content (setup through Express.js error handling) based on available excerpts. The later units on user authentication, database integration, and production deployment are mentioned but not detailed here. --- ##