Modern JavaScript is a very different language from the one that earned its messy reputation. Since ES2015 the language has gained modules, destructuring, spread syntax, optional chaining, and a far saner standard library, and Node now supports all of it natively. This lesson covers the core syntax you will lean on daily when building product features.
Modules and Import Syntax in Node
Node supports both CommonJS require calls and ES modules with import and export statements. New projects should default to ES modules by setting the type field to module in package.json. Named exports keep dependencies explicit and make refactoring safer, while default exports are best reserved for a file whose whole purpose is one thing, such as a single Express router.
Destructuring and Spread in Real Code
Destructuring lets you pull fields out of objects and arrays in one line, which matters constantly when handling API payloads. Writing const { userId, prompt } = req.body is clearer than repeated property access. Spread syntax copies and merges objects immutably, a habit that prevents an entire class of shared-state bugs in request handlers.
Optional Chaining and Nullish Coalescing
Production data is messy, and deeply nested response objects from third-party APIs often have missing branches. Optional chaining with the question-mark-dot operator short-circuits safely, and the double-question-mark operator supplies defaults only when a value is null or undefined, unlike the logical OR operator which also overrides zero and empty strings.
Action Step
Take a small script you have written before, convert it to ES modules, and refactor at least three property accesses to use destructuring and optional chaining.
Educational content only — practical career training; not professional advice, and no specific job, salary, or business outcome is implied.