Best of V8 — 2025

  1. 1
    Article
    Avatar of nodejsNode.js·31w

    Node.js — Node.js v25.1.0 (Current)

    Node.js v25.1.0 introduces several minor enhancements including an HTTP server option to optimize empty requests, SQLite defensive flag configuration, and a watch config namespace. The release includes updates to root certificates (NSS 3.116), dependency updates for simdjson, corepack, and inspector_protocol, plus V8 visibility improvements. Additional changes cover module loading refactoring, inspector network payload limits, test improvements, and build system updates including Visual Studio 2022 upgrade for Windows.

  2. 2
    Article
    Avatar of nodejsNode.js·28w

    Node.js — Node.js v25.2.1 (Current)

    Node.js v25.2.1 has been released, reverting a spec-compliant behavior change that threw errors on localStorage access. The team determined this breaking change was too disruptive for a semver-minor release and postponed it to version 26.0.0. The release includes fixes for RSA-PSS saltLength defaults in crypto, a V8 backport, and clarifications on the experimental status of Web Storage support.

  3. 3
    Article
    Avatar of nodejsNode.js·24w

    Node.js — Node.js v24.12.0 (LTS)

    Node.js v24.12.0 (LTS) 'Krypton' has been released with several notable changes including HTTP server optimization options, stable type stripping support, new Node-API object creation methods, SQLite defensive flag configuration, watch mode configuration namespace, portable compile cache options, inspector permission controls, and V8 CPU profiling capabilities. The release includes numerous bug fixes, performance improvements, and dependency updates across modules like crypto, buffer, console, and testing infrastructure.

  4. 4
    Article
    Avatar of platformaticPlatformatic·1y

    Boost Node.js with V8 GC Optimization

    Optimizing memory management in Node.js using V8's garbage collector is crucial for preventing performance issues and crashes. The post highlights the importance of tuning the Young Generation size to avoid premature promotion of objects, which can degrade application performance. Adjusting the --max-semi-space-size flag helps balance memory usage and computational efficiency, especially in memory-constrained environments like containers. Properly configuring V8 can reduce CPU time and garbage collection pauses, improving application latency and throughput.

  5. 5
    Article
    Avatar of v8V8·43w

    How we made JSON.stringify more than twice as fast · V8

    V8 engineers achieved a 2x performance improvement in JSON.stringify by implementing a side-effect-free fast path that bypasses expensive checks for common data objects. Key optimizations include templated string handling for different character encodings, SIMD instructions for string escaping detection, hidden class caching for object properties, replacing the Grisu3 algorithm with Dragonbox for number conversion, and using segmented buffers to eliminate costly memory reallocations. The improvements are available in V8 13.8 and benefit most typical JSON serialization use cases automatically.

  6. 6
    Article
    Avatar of nodelandAdventures in Nodeland·32w

    Noop Functions vs Optional Chaining: A Performance Deep Dive

    Benchmarks reveal that noop functions are 5.5x to 8.8x faster than optional chaining in JavaScript, executing at 939 million ops/second versus 106-169 million ops/second. The performance gap stems from V8's ability to inline noop functions while optional chaining requires runtime null/undefined checks that can't be optimized away. Frameworks like Fastify leverage this by providing noop logger objects instead of checking for existence. While optional chaining remains suitable for most code due to safety and readability benefits, noop functions offer measurable gains in hot paths and high-frequency operations. TypeScript's strict null checks can push developers toward unnecessary optional chaining when runtime guarantees exist.

  7. 7
    Video
    Avatar of t3dotggTheo - t3․gg·41w

    JSON just got way better (yes really)

    Chrome's V8 engine has dramatically improved JSON.stringify performance by up to 3x through several optimizations: a new side-effect-free fast path that bypasses expensive checks, specialized string handling for one-byte vs two-byte characters, SIMD instructions for escape character detection, hidden class caching for repeated object shapes, segmented buffer allocation to eliminate copying overhead, and upgrading to the DragonBox algorithm for number-to-string conversion. These improvements are available in Chrome 138 and benefit most common JSON serialization use cases automatically.

See all V8 archives