This meant you could pipe fetch responses directly to file streams using a standard API:
Let's look under the hood. 1. Native Fetch API (No More node-fetch ) For years, making an HTTP request in Node meant one of two things: installing node-fetch or using axios . It felt archaic that the runtime didn't include the same fetch your browser had.
Upgrade your dependencies or use --openssl-legacy-provider (not recommended for production). The node: Protocol Node 18 strongly encourages using the node: import prefix for built-in modules. This is mandatory if you use ES modules ( "type": "module" in package.json ).
For small microservices or internal tools, Node 18's test runner eliminated configuration fatigue. No more jest.config.js , no more mocha --timeout . Just node --test and go. Streaming in Node has always been powerful but verbose. Node 18 shipped the Web Streams API as a global, matching the spec used in browsers.
Because understanding Node 18 is the key to understanding the modern Node.js you use today. It wasn't just another release; it was a paradigm shift.
Node 18 reached EOL (End of Life) in April 2025. That means no more security patches. Running it today is a security risk unless your app is completely offline.
This meant you could pipe fetch responses directly to file streams using a standard API:
Let's look under the hood. 1. Native Fetch API (No More node-fetch ) For years, making an HTTP request in Node meant one of two things: installing node-fetch or using axios . It felt archaic that the runtime didn't include the same fetch your browser had. node 18
Upgrade your dependencies or use --openssl-legacy-provider (not recommended for production). The node: Protocol Node 18 strongly encourages using the node: import prefix for built-in modules. This is mandatory if you use ES modules ( "type": "module" in package.json ). This meant you could pipe fetch responses directly
For small microservices or internal tools, Node 18's test runner eliminated configuration fatigue. No more jest.config.js , no more mocha --timeout . Just node --test and go. Streaming in Node has always been powerful but verbose. Node 18 shipped the Web Streams API as a global, matching the spec used in browsers. It felt archaic that the runtime didn't include
Because understanding Node 18 is the key to understanding the modern Node.js you use today. It wasn't just another release; it was a paradigm shift.
Node 18 reached EOL (End of Life) in April 2025. That means no more security patches. Running it today is a security risk unless your app is completely offline.