Node.js 26.8.0 adds native ZIP archives to core, a GCM-SIV mode for Ciphers, and a stable TracingChannel, so tooling authors can drop a native dependency and you can build observability on an API that will not move.
Node.js 26.8.0 lands first-class ZIP support in the standard library through the new zlib.ZipEntry, ZipFile, and ZipBuffer classes. For anyone shipping a CLI or bundler that reads or writes archives, this is the one to care about: native ZIP read and write removes a native dependency that has been a recurring headache for tooling authors.
The Cipher and Decipher APIs also gain SIV and GCM-SIV modes, giving you a constant-time authenticated encryption option with no third-party crypto library. diagnostics_channel.TracingChannel graduates to stable, so you can build request tracing and instrumentation on it without hedging on a still-moving API.
Two smaller additions are worth a look. util.MIMEType.parse is now non-throwing, so parsing a malformed content type will not throw in your request path. The REPL gets basic syntax highlighting, a quiet win if you live in a terminal.
The rest is housekeeping: root certificates move to NSS 3.126 and net.BlockList gets a performance pass for matching IPs in large lists. Ignore both unless you run a heavily filtered server. Antoine du Hamel cut this Current release, so point your CI at it and check whether the ZIP API covers the archive handling you have been pulling dependencies in for.
Vite+ Beta bundles Vite 7, a runtime, and a package manager into a single workflow with smart caching and a migration CLI, targeting teams tired of stitching together separate build, run, and dependency tools.
1 source
React 19.3 stabilizes `<ViewTransition>`, which drives enter, exit, move, and resize animations via the browser's View Transition API without a flag, and adds `browser()` from `react-dom` for components that should not render on the server.
1 source
Bun 1.4 is the first stable release on the new Rust runtime, passing 1,517 more Node.js tests and cutting idle CPU use 5x, so it is time to re-run your Node replacement benchmarks.
1 source