Node.js 8.x: What's New, Release History & EOL Status

What Is New in Node.js 8?

async/await Natively Available -- The Biggest Change in Modern Node.js

Node.js 8 ships with V8 5.7, making async/await natively available without flags or transpilation. This is arguably the most impactful developer experience improvement in Node.js history -- switching from nested callbacks and promise chains to readable, sequential-looking async code.

// Before async/await
function getUser(id) {
  return db.findOne({ id })
    .then(user => permissions.load(user))
    .then(perms => ({ ...user, perms }));
}

// With async/await in Node.js 8
async function getUser(id) {
  const user = await db.findOne({ id });
  const perms = await permissions.load(user);
  return { ...user, perms };
}

V8 Inspector Stable -- Node.js Debugging in Chrome DevTools

The V8 Inspector protocol is stable in Node.js 8. Running node --inspect server.js starts the debugger endpoint. You can then open chrome://inspect in Chrome to attach, set breakpoints, inspect memory, and profile CPU -- all without extra tools.

node --inspect server.js
# or break on first line:
node --inspect-brk script.js

WHATWG URL API

Node.js 8 introduces the WHATWG URL class (the same standard as browsers). It replaces the older url.parse() with a spec-compliant implementation that handles relative URLs, search params, and unicode domains correctly.

const url = new URL('https://example.com/path?q=hello&page=2');
console.log(url.hostname);   // example.com
console.log(url.searchParams.get('q')); // hello

Buffer Safety -- Buffer.alloc() Over new Buffer()

The Buffer() constructor is deprecated in Node.js 8. The replacement APIs are Buffer.alloc(size) (zero-filled), Buffer.allocUnsafe(size) (uninitialized, faster), and Buffer.from(data). The old constructor was a security risk because it could expose uninitialized memory from the heap.