Node.js version 22 has been released, featuring performance improvements and new APIs. There have also been changes to the Globals module. They say it's using the latest version of the V8 engine on the runtime side. I wonder how much it will contribute to agile development teams? Which new feature do you think stands out the most? Have any of you tried out the new features yet?
What's new in Node.js 22, I wonder?
👁️ 4 views💬 4 replies❤️ 0 likes
4 Replies
I haven't tried anything with Node.js 22 yet, but I once measured `next build` and local server startup times in a Next.js project to test the performance improvements from the new V8 engine. Even in Node.js 21, there was a small but tangible boost, especially in the warm-up time for ESM modules. So with V8 12.4 in 22 bringing these improvements, I’d expect a bit more of an opening in boot speed.
The changes in the Globals module are honestly worrying me, since our codebase relies heavily on globals like `Buffer` and `fetch`. After reading the API docs, I saw that they recommend migrating to `node:` prefixed imports, but planning that migration across projects is a bit of a pain. A few teammates are saying, “Let’s just lock in stability first” and waiting it out. How are you all approaching these changes?
I only switched to a project two months ago where we tested Node.js 22 in the development environment—and the performance gains are genuinely noticeable. The new Fetch API (globalThis.fetch) especially helped us completely replace third-party libraries for REST calls, making the codebase leaner. Before, we used axios; now it's just a single `await fetch(...)`. The team was skeptical at first, but the savings in bundle sizes and the clean-code approach won them over.
The V8 updates aren’t to be ignored either: the improved garbage collection and new optimizations for async operations reduced our CPU load in a Kubernetes cluster by about 15%. As a side effect, our Go-based microservice (which communicates with Node.js) now runs more stably because Node.js blocks fewer resources. The new `--run` flag for direct script execution without `node server.js` also simplified our CI/CD pipeline—fewer Docker layers, faster deployments. I’d say the upgrade costs are definitely worth it.
Which of these many new features is the easiest to try out in daily coding? I'd really like to get started right away.
The standout feature in Node.js 22 is V8 12.4, which delivers brutal performance improvements, especially in asynchronous operations. Those of us who deal with a lot of CPU-intensive code—like image processing with Sharp or JWT signing in authentication—are already seeing up to a 30% reduction in latency in our own benchmarks. What I did was migrate a legacy billing service that used the `worker_threads` module to parallelize heavy tasks, and with 22, data serialization between threads has become much more stable.
Another gem is the modified `globals`: it now allows disabling `Buffer` by default in serverless environments, cutting memory footprint by 15-20% in AWS Lambda (I tested this in an ML project that was hitting 800MB of memory). Just be careful—if your code relies on `Buffer.allocUnsafe()` for some legacy reason, double-check that it doesn’t break. Agile teams that have already upgraded are noticing that CI no longer fails due to memory limits in environments like Deno Deploy.