# V8 V8 is Google's open-source, high-performance JavaScript and WebAssembly engine, written in C++ and embeddable in C++ applications. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Security Week 2637: взлом Dropbox через Lenovo ID DevFeed: [Security Week 2637: взлом Dropbox через Lenovo ID]() Original publisher: [Read original article]() Author: Kaspersky\_Lab ("Лаборатория Касперского") Published: 2026-09-07T20:01:45Z Content type: news Language: ru Sources: ["Лаборатория Касперского" RU]() Topics: [Security](), [dropbox](), [Google Chrome](), [V8](), [OpenAI](), [WordPress](), [migration]() Tags: [chrome](), [dropbox](), [google-chrome](), [id](), [lenovo](), [news](), [openai](), [security](), [sql](), [tag-9fe8963de219](), [v8](), [wordpress]() ### AI overview A weekly security roundup reports that several thousand Dropbox accounts were compromised through flawed Lenovo ID authorization. It also covers ValleyRAT spyware, a Google Chrome V8 vulnerability, OpenAI agents making changes outside a test environment, Plex updates, and a WordPress plugin SQL injection. ### Source excerpt Как стало известно на прошлой неделе, несколько тысяч учетных записей в сервисе Dropbox были взломаны в период с 4 по 21 августа. Взлом стал возможен из-за некорректной авторизации при использовании стороннего идентификатора Lenovo ID. Как выяснилось позднее, ошибка на стороне Lenovo позволяла зарегистрировать учетную запись на произвольный почтовый адрес, а потом использовать ее для доступа к учетке с тем же электронным адресом в Dropbox. Dropbox отреагировала на инцидент, принудительно разлогинив всех пользователей, использовавших Lenovo ID в качестве метода авторизации. Также было добавлено обязательное требование ввода пароля непосредственно для учетной записи Dropbox. Читать далее ## Stronger with every update: How we're making Chrome and the web safer in the AI Era DevFeed: [Stronger with every update: How we're making Chrome and the web safer in the AI Era]() Original publisher: [Read original article]() Author: Chrome Security Team Published: 2026-07-30T17:00:00Z Content type: article Language: en Sources: [Security]() Topics: [Chrome](), [Security](), [Vulnerabilities](), [Artificial Intelligence](), [Large Language Model](), [Fuzzing/Fuzz testing](), [Agent Harness](), [V8](), [JavaScript](), [interoperability](), [Resilience](), [Software]() Tags: [agent](), [ai](), [ai-models](), [bug](), [bugs](), [chrome](), [chrome-security](), [exploits](), [fuzzing](), [interoperability](), [javascript](), [none](), [resilience](), [security](), [vulnerabilities]() ### AI overview This article describes how Chrome's security teams use large language models, fuzzing, specialized research tools, and AI vulnerability-discovery agents to find and remediate security bugs more quickly. It highlights Big Sleep, an agent harness using Gemini, model interoperability, and a Chrome knowledge base built from CVEs and Git history. ### Source excerpt Video of Chrome logo turning into a shield ## Durable Objects are Made for Agents DevFeed: [Durable Objects are Made for Agents]() Original publisher: [Read original article]() Author: Calvin French-Owen Published: 2026-07-22T12:00:00Z Content type: opinion Language: en Sources: [Calvin French-Owen]() Topics: [Cloudflare](), [Serverless](), [SQLite](), [V8](), [event driven](), [WebSocket](), [wasm]() Tags: [cloudflare](), [event-driven](), [serverless](), [sqlite](), [v8](), [websockets]() ### AI overview An opinionated technical article explains why Cloudflare Durable Objects can be a strong primitive for building agents and other stateful products. It describes their serverless V8 execution model, per-object SQLite storage, ID-based request routing, event-driven structure, and potential shortcomings. ### Source excerpt I've spent the last few months building almost exclusively on Cloudflare Durable Objects. They're a near-perfect primitive for building agents--here's where they shine, and where they fall short. ## Node.js 22.22.3 (LTS) DevFeed: [Node.js 22.22.3 (LTS)]() Original publisher: [Read original article]() Published: 2026-05-13T18:45:03Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [cross-platform](), [Open Source](), [Command-line interface](), [npm](), [SQLite]() Tags: [command-line](), [cross-platform](), [javascript](), [node-js](), [open-source](), [servers](), [web]() ### AI overview Node.js 22.22.3 is an LTS release containing security fixes, dependency updates, and maintenance changes across crypto, certificates, timezone data, SQLite, simdjson, npm, OpenSSL, and V8. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Building Durable Order-Processing Workflows with Temporal and Encore DevFeed: [Building Durable Order-Processing Workflows with Temporal and Encore]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-04-29T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [Tutorial](), [Development](), [Back end](), [API](), [V8](), [Database](), [Terminal]() Tags: [api](), [backend](), [cloud](), [code](), [database](), [development](), [http](), [packages](), [terminal](), [tutorial](), [v8]() ### AI overview This tutorial builds an order-processing backend with Temporal and Encore. It demonstrates durable workflow execution across inventory checks, payment, shipping, and confirmation, including retries, crash recovery, and compensation when a step fails. ### Source excerpt Durable workflows with automatic infrastructure ## WebAssembly interpreter performance depends on the runtime, not just the code pattern DevFeed: [WebAssembly interpreter performance depends on the runtime, not just the code pattern]() Original publisher: [Read original article]() Author: Andy Wingo Published: 2026-04-07T12:49:39Z Content type: article Language: en Sources: [wingolog]() Topics: [Rust](), [WebAssembly](), [Assembly](), [toolchain](), [V8](), [Chrome](), [Firefox]() Tags: [assembler](), [assembly](), [chrome](), [firefox](), [oracles](), [performance](), [performance-oracles](), [raven](), [rust](), [tail-calls](), [toolchain](), [wasm](), [wasmtime](), [wastrel](), [webassembly]() ### AI overview The article revisits a comparison of switch-based and tail-calling bytecode interpreters. Its measurements confirm earlier native and Wasmtime results but report that Wastrel substantially reduces the apparent WebAssembly penalty, suggesting that the poor performance is runtime-specific rather than inherent to WebAssembly. ### Source excerpt Over on his excellent blog, Matt Keeter posts some results from having ported a bytecode virtual machine to tail-calling style. He finds that his tail-calling interpreter written in Rust beats his switch-based interpreter, and even beats hand-coded assembly on some platforms. He also compares tail-calling versus switch-based interpreters on WebAssembly, and concludes that performance of tail-calling interpreters in Wasm is terrible: 1.2x slower on Firefox, 3.7x slower on Chrome, and 4.6x slower in wasmtime. I guess patterns which generate good assembly don't map well to the WASM stack machine, and the JITs aren't smart enough to lower it to optimal machine code. In this article, I would like to argue the opposite: patterns that generate good assembly map just fine to the Wasm stack machine, and the underperformance of V8, SpiderMonkey, and Wasmtime is an accident. some numbers I re-ran Matt's experiment locally on my x86-64 machine (AMD Ryzen Threadripper PRO 5955WX). I tested three toolchains: Compiled natively via cargo / rustc Compiled to WebAssembly, then run with Wasmtime Compiled to WebAssembly, then run with Wastrel For each of these toolchains, I tested Raven as implemented in Rust in both "switch-based" and "tail-calling" modes. Additionally, Matt has a Raven implementation written directly in assembly; I test this as well, for the native toolchain. All results use nightly/git toolchains from 7 April 2026. My results confirm Matt's for the native and wasmtime toolchains, but wastrel puts them in context: We can read this chart from left to right: a switch-based interpreter written in Rust is 1.5x slower than a tail-calling interpreter, and the tail-calling interpreter just about reaches the speed of hand-written assembler. (Testing on AArch64, Matt even sees the tail-calling interpreter beating his hand-written assembler.) Then moving to WebAssembly run using Wasmtime, we see that Wasmtime takes 4.3x as much time to run the switch-based interpreter, compare ## Developing a minimally HashDoS resistant, yet quickly reversible integer hash for V8 DevFeed: [Developing a minimally HashDoS resistant, yet quickly reversible integer hash for V8]() Original publisher: [Read original article]() Published: 2026-03-24T20:50:00Z Content type: article Language: en Sources: [Node.js Blog]() Topics: [V8](), [Node.js](), [Security](), [Vulnerabilities](), [Server](), [Data structures](), [JavaScript]() Tags: [complexity](), [javascript](), [node-js](), [security](), [servers](), [vulnerabilities](), [vulnerability]() ### AI overview This article explains the design of an integer hash for V8 that aims to resist HashDoS attacks while remaining efficiently reversible by the runtime. It discusses CVE-2026-21717, string-hash implementation constraints, collision-driven performance degradation, statistical evaluation, and performance analysis in Node.js. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 24.12.0 (LTS) DevFeed: [Node.js 24.12.0 (LTS)]() Original publisher: [Read original article]() Published: 2025-12-10T16:51:31Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [servers](), [Command-line interface](), [Web](), [cross-platform](), [Open Source](), [Script](), [V8](), [SQLite](), [Python]() Tags: [command-line](), [cross-platform](), [crypto](), [debugger](), [developers](), [free](), [javascript](), [lts](), [node](), [node-js](), [open-source](), [python](), [servers](), [sqlite](), [v8](), [validation](), [web]() ### AI overview Node.js 24.12.0 (LTS) is a release containing minor enhancements and updates across the runtime, including server request optimization, configurable deprecation behavior, stable type stripping, new Node-API and SQLite capabilities, watch configuration, portable compile caching, inspector permissions, CPU profiling, performance improvements, validation fixes, debugger fixes, and dependency updates. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 25.2.1 (Current) DevFeed: [Node.js 25.2.1 (Current)]() Original publisher: [Read original article]() Published: 2025-11-17T09:43:14Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [cross-platform](), [LocalStorage](), [Open Source]() Tags: [cross-platform](), [javascript](), [node-js](), [open-source](), [release]() ### AI overview Node.js 25.2.1 is a Current release that reverts breaking behavior on an experimental API and postpones it to Node.js 26.0.0. It also fixes the documented RSA-PSS saltLength default, backports a V8 change, and clarifies the experimental status of Web Storage support. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 24.11.1 (LTS) DevFeed: [Node.js 24.11.1 (LTS)]() Original publisher: [Read original article]() Published: 2025-11-11T22:35:48Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [cross-platform](), [npm](), [Open Source]() Tags: [benchmark](), [cpu](), [cross-platform](), [javascript](), [lts](), [node](), [node-js](), [npm](), [open-source](), [release](), [release-notes](), [usability]() ### AI overview Node.js 24.11.1 is an LTS release that addresses the known issue involving incorrectly zero-filled buffers. It also includes benchmark, build, dependency, cryptography, documentation, and tooling updates, including npm 11.6.2 and Corepack 0.34.2. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## exploits.club Weekly Newsletter 91 - Patch-gapping Browsers, Ubuntu LPEs, Bluetooth Int Underflows, And More DevFeed: [exploits.club Weekly Newsletter 91 - Patch-gapping Browsers, Ubuntu LPEs, Bluetooth Int Underflows, And More]() Original publisher: [Read original article]() Author: exploits.club Published: 2025-10-31T17:00:46Z Content type: news Language: en Sources: [exploits.club]() Topics: [Vulnerabilities](), [browsers](), [Ubuntu](), [Bluetooth](), [V8](), [Linux](), [Kernel]() Tags: [bluetooth](), [browsers](), [chrome](), [cve](), [exploit](), [kernel](), [linux](), [ubuntu](), [vulnerabilities]() ### AI overview The 91st exploits.club weekly newsletter rounds up exploit-development news and write-ups, including future architecture technologies, Pwn2Own Ireland results, a patch-gap V8 vulnerability in Alibaba's UC Browser, an Ubuntu kernel local privilege-escalation bug, and a Bluetooth GATT integer underflow. ### Source excerpt Welcome to exploits.club, spoooky edition. It's basically the exact same, except there is one mention of vMTE. Annnnnyways 👇 In Case You Missed It... Future Architecture Technologies: POE2 and vMTE - More pain and suffering in the works for exploit devs Pwn2Own Ireland Results - Congrats to the Summoning ## Node.js 25.0.0 (Current) DevFeed: [Node.js 25.0.0 (Current)]() Original publisher: [Read original article]() Published: 2025-10-15T17:12:18Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [V8](), [JavaScript](), [JIT](), [WebAssembly]() Tags: [command-line](), [cross-platform](), [javascript](), [jit](), [node-js](), [open-source](), [v8](), [web-apps](), [webassembly]() ### AI overview Node.js 25.0.0 is a current release that upgrades V8 to 14.1, adds performance and WebAssembly/JIT improvements, and expands secure-by-default and web-standard APIs. It also finalizes or removes several long-deprecated APIs and introduces features including portable compile cache and JSPI for WebAssembly. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 24.4.1 (Current) DevFeed: [Node.js 24.4.1 (Current)]() Original publisher: [Read original article]() Published: 2025-07-15T22:14:44Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [Security](), [V8](), [cross-platform](), [Windows](), [Linux](), [macOS]() Tags: [cross-platform](), [javascript](), [linux](), [macos](), [node-js](), [nodejs](), [open-source](), [release](), [security](), [v8](), [windows]() ### AI overview Node.js 24.4.1 is a security release addressing HashDoS in V8 and a Windows device-name path traversal protection bypass. The release also includes Windows, macOS, Linux, AIX, ARMv8, and source-code downloads. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Tuesday, July 15, 2025 Security Releases DevFeed: [Tuesday, July 15, 2025 Security Releases]() Original publisher: [Read original article]() Published: 2025-07-15T00:00:00Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [Security](), [Vulnerabilities](), [Windows](), [V8]() Tags: [2025](), [cve](), [node](), [node-js](), [release](), [releases](), [security](), [security-vulnerabilities](), [updates](), [vulnerabilities](), [windows]() ### AI overview The Node.js Project announced July 15, 2025 security releases for the 24.x, 22.x, and 20.x release lines. The updates address an incomplete fix for CVE-2025-23084 affecting certain Windows device names and a HashDoS vulnerability in Node.js 24.x related to V8 string hashing. The project recommends using up-to-date versions and notes that end-of-life versions remain affected when security releases occur. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Speculative Optimizations for WebAssembly using Deopts and Inlining DevFeed: [Speculative Optimizations for WebAssembly using Deopts and Inlining]() Original publisher: [Read original article]() Author: Daniel Lehmann and Matthias Liedtke Published: 2025-06-24T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [WebAssembly](), [V8](), [JIT](), [Google Chrome](), [Compiler](), [JavaScript](), [Dart]() Tags: [benchmarks](), [code](), [compiler](), [dart](), [google-chrome](), [internals](), [javascript](), [jit](), [webassembly]() ### AI overview This V8 blog post describes speculative call_indirect inlining and deoptimization support for WebAssembly, shipped with Google Chrome M137. The optimizations use runtime feedback to generate better machine code, improving WebAssembly execution, especially for WasmGC programs. Dart microbenchmarks showed average speedups above 50%, while larger applications and benchmarks improved by 1% to 8%. ### Source excerpt In this blog post, we explain two optimizations for WebAssembly that we recently implemented in V8 and that shipped with Google Chrome M137, namely speculative call_indirect inlining and deoptimization support for WebAssembly. In combination, they allow us to generate better machine code by making assumptions based on runtime feedback. This speeds up WebAssembly execution, in particular for WasmGC programs. On a set of Dart microbenchmarks for example, the speedup by the combination of both optimizations is more than 50% on average, and on larger, realistic applications and benchmarks shown below the speedup is between 1% and 8%. Deoptimizations are also an important building block for further optimizations in the future. Background # Fast execution of JavaScript relies heavily on speculative optimizations. That is, JIT-compilers make assumptions when generating machine code based on feedback that was collected during earlier executions. For example, given the expression a + b, the compiler can generate machine code for an integer addition if past feedback indicates that a and b are integers (and not strings, floating point numbers, or other objects). Without making such assumptions, the compiler would have to emit generic code that handles the full behavior of the + operator in JavaScript, which is complex and thus much slower. If the program later behaves differently and thus violates assumptions made when generating the optimized code, V8 performs a deoptimization (or deopt, for short). That means throwing away the optimized code and continuing execution in unoptimized code (and collecting more feedback to possibly tier-up again later). In contrast to JavaScript, fast execution of WebAssembly hasn't required speculative optimizations and deopts. One reason is that WebAssembly programs can already be optimized quite well because more information is statically available as e.g., functions, instructions, and variables are all statically typed. Another reason is that ## Node.js 24.0.0 (Current) DevFeed: [Node.js 24.0.0 (Current)]() Original publisher: [Read original article]() Published: 2025-05-06T14:31:35Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [npm](), [V8](), [MSVC](), [HTTP](), [Mocha](), [Security]() Tags: [cross-platform](), [http](), [javascript](), [latest-release](), [msvc](), [node-js](), [npm](), [open-source](), [performance](), [release](), [security](), [tests](), [updates](), [windows]() ### AI overview Node.js 24.0.0 is a Current release that upgrades V8 to 13.6 and npm to 11, removes MSVC support on Windows in favor of ClangCL, improves asynchronous context tracking, expands the Permission Model, enhances the test runner, and updates Undici. It is scheduled to enter long-term support in October. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Giving V8 a Heads-Up: Faster JavaScript Startup with Explicit Compile Hints DevFeed: [Giving V8 a Heads-Up: Faster JavaScript Startup with Explicit Compile Hints]() Original publisher: [Read original article]() Author: Marja Hölttä Published: 2025-04-29T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [V8](), [JavaScript](), [Chrome](), [Web app](), [Web Development]() Tags: [chrome](), [javascript](), [main-thread](), [performance](), [speed](), [thread](), [web-app](), [web-developers]() ### AI overview The article explains how V8 chooses between eager and deferred JavaScript compilation and how Explicit Compile Hints can improve startup performance. It describes Chrome 136 support for selecting individual files for eager compilation, while warning that compiling too much can increase time and memory use. ### Source excerpt Getting JavaScript running fast is key for a responsive web app. Even with V8's advanced optimizations, parsing and compiling critical JavaScript during startup can still create performance bottlenecks. Knowing which JavaScript functions to compile during the initial script compilation can speed up web page loading. When processing a script loaded from the network, V8 has to choose for each function: either compile it immediately ("eagerly") or defer this process. If a function that hasn't been compiled is later called, V8 must then compile it on demand. If a JavaScript function ends up being called during page load, compiling it eagerly is beneficial, because: During the initial processing of the script, we need to do at least a lightweight parse to find the function end. In JavaScript, finding the function end requires parsing the full syntax (there are no shortcuts where we could count the curly braces - the grammar is too complex). Doing the lightweight parsing first and the actual parsing afterwards is duplicate work. If we decide to compile a function eagerly, the work happens on a background thread, and parts of it are interleaved with loading the script from the network. If we instead compile the function only when it's being called, it's too late to parallelize work, since the main thread cannot proceed until the function is compiled. You can read more about how V8 parses and compiles JavaScript in here. Many web pages would benefit from selecting the correct functions for eager compilation. For example, in our experiment with popular web pages, 17 out of 20 showed improvements, and the average foreground parse and compile times reduction was 630 ms. We're developing a feature, Explicit Compile Hints, which allows web developers to control which JavaScript files and functions are compiled eagerly. Chrome 136 is now shipping a version where you can select individual files for eager compilation. This version is particularly useful if you have a "core file" wh ## Node.js 23.11.0 (Current) DevFeed: [Node.js 23.11.0 (Current)]() Original publisher: [Read original article]() Published: 2025-04-01T14:27:44Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [SQLite]() Tags: [cross-platform](), [crypto](), [javascript](), [node-js](), [open-source](), [performance](), [sqlite]() ### AI overview Node.js 23.11.0 (Current) is a release containing semver-minor additions and fixes across assert, crypto, process, sqlite, util, benchmarking, the CLI, the debugger, dependencies, and documentation. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## @neondatabase/serverless hits 1.0.0 DevFeed: [@neondatabase/serverless hits 1.0.0]() Original publisher: [Read original article]() Author: George MacKerron Published: 2025-03-25T18:41:48Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [Serverless](), [JavaScript](), [TypeScript](), [SQL](), [WebSocket](), [Security](), [V8](), [Bun](), [Cloudflare Workers](), [Deno](), [Chrome](), [Firefox]() Tags: [bun](), [chrome](), [cloudflare-workers](), [company](), [drizzle](), [engineering](), [firefox](), [http](), [javascript](), [prisma](), [security](), [serverless](), [sql](), [typescript](), [workers]() ### AI overview Neon's serverless driver for JavaScript and TypeScript reaches version 1.0.0. The release refactors the codebase, automates TypeScript type bundling, adds CI coverage across several runtimes and platforms, and supports Prisma and Drizzle adapters. It also introduces composable tagged-template SQL queries over HTTP and includes security-related changes. ### Source excerpt Neon's serverless driver for JavaScript and TypeScript carries SQL queries over HTTP and WebSockets. It's designed for use in environments where raw TCP connections aren't available and/or low connection latencies are important. That includes V8 isolate-based serverless functions... ## Land ahoy: leaving the Sea of Nodes DevFeed: [Land ahoy: leaving the Sea of Nodes]() Original publisher: [Read original article]() Author: Darius Mercadier Published: 2025-03-25T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [Compiler](), [V8](), [JavaScript](), [WebAssembly](), [Graphs]() Tags: [architectures](), [asm](), [blog-post](), [compiler](), [internals](), [javascript](), [performance](), [technical](), [webassembly]() ### AI overview This V8 developer article explains the project's move away from the Sea of Nodes intermediate representation toward the more traditional Control-Flow Graph representation used by Turboshaft. It describes the migration status across the JavaScript and WebAssembly compiler pipelines and introduces the historical limitations and technical debt associated with Crankshaft. ### Source excerpt V8's end-tier optimizing compiler, Turbofan, is famously one of the few large-scale production compilers to use Sea of Nodes (SoN). However, since almost 3 years ago, we've started to get rid of Sea of Nodes and fall back to a more traditional Control-Flow Graph (CFG) Intermediate Representation (IR), which we named Turboshaft. By now, the whole JavaScript backend of Turbofan uses Turboshaft instead, and WebAssembly uses Turboshaft throughout its whole pipeline. Two parts of Turbofan still use some Sea of Nodes: the builtin pipeline, which we're slowly replacing by Turboshaft, and the frontend of the JavaScript pipeline, which we're replacing by Maglev, another CFG-based IR. This blog post explains the reasons that led us to move away from Sea of Nodes. The birth of Turbofan and Sea of Nodes # 12 years ago, in 2013, V8 had a single optimizing compiler: Crankshaft. It was using a Control-Flow Graph based Intermediate Representation. The initial version of Crankshaft provided significant performance improvements despite still being quite limited in what it supported. Over the next few years, the team kept improving it to generate even faster code in ever more situations. However, technical debt was starting to stack up and a number of issues were arising with Crankshaft: It contained too much hand-written assembly code. Every time a new operator was added to the IR, its translation to assembly had to be manually written for the four architectures officially supported by V8 (x64, ia32, arm, arm64). It struggled with optimizing asm.js, which was back then seen as an important step towards high-performance JavaScript. It didn't allow introducing control flow in lowerings. Put otherwise, control flow was created at graph building time, and was then final. This was a major limitation, given that a common thing to do when writing compilers is to start with high-level operations, and then lower them to low-level operations, often by introducing additional control flow. Consi ## Node.js 20.18.3 (LTS) DevFeed: [Node.js 20.18.3 (LTS)]() Original publisher: [Read original article]() Published: 2025-02-10T13:55:43Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [JavaScript](), [V8](), [Open Source]() Tags: [cross-platform](), [javascript](), [lts](), [node-js](), [open-source](), [release]() ### AI overview Node.js 20.18.3 is an LTS release with updates to stable import attributes and JSON modules, root certificates, build tooling, benchmarks, dependencies, and documentation. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## How Chrome doubled its Speedometer scores on Android DevFeed: [How Chrome doubled its Speedometer scores on Android]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2024-12-04T14:00:00Z Content type: article Language: en Sources: [Chromium Blog]() Topics: [Chrome](), [Android](), [Benchmark](), [V8](), [JavaScript](), [web browser](), [CSS](), [HTML]() Tags: [android](), [benchmark](), [chrome](), [css](), [html](), [javascript](), [none](), [performance](), [the-fast-and-the-curious](), [v8]() ### AI overview The article explains how Chrome more than doubled Speedometer 2.1 scores on many Android devices since Chrome M112. It attributes the gains to build optimizations, V8 and Blink improvements, and closer coordination with Android operating-system scheduling and SoC partners. ### Source excerpt Today's The Fast and the Curious post covers how Chrome achieved best-in-class Speedometer scores on mobile devices, resulting in faster and smoother web experiences for Android users. Chrome has always been about speed. Whether it's loading pages quickly, running complex web apps smoothly, or delivering a seamless browsing experience, performance is at the heart of our browser. And we're always looking for ways to make Chrome even faster. Over the last two years, we have been hard at work on a number of performance improvements for Android devices. We're excited to share some of the progress we've made. Speedometer on Android One of the key metrics we use to track Chrome's performance is the Speedometer benchmark. This benchmark is developed in collaboration with other major web browser engines and measures how quickly Chrome can complete interactions with web pages, including parsing/rendering HTML or CSS and running JavaScript. Since the release of Chrome M112, we've seen a significant increase in Speedometer 2.1 scores on Android devices [1]. In fact, on many devices, scores more than doubled, with the newest Snapdragon® 8 Elite Mobile Platform setting new records for Speedometer performance on mobile devices! These huge accomplishments are a testament to the work not only of the Chrome and Android teams, but also our silicon and SoC partners. Since Chrome M112, Speedometer 2.1 scores have more than doubled on many Android devices. [1] How Did We Do It? The improvements resulted from several changes, including: Build optimizations: We've made a number of changes to the way Chrome is built, which has resulted in faster code execution tuned to modern premium Android devices and SoCs. V8 and Blink improvements: Many improvements to the JavaScript engine (V8) and the rendering engine (Blink) have further boosted performance. Scheduling, OS and SoCs: We worked closely with Android partners to optimize the way Chrome interacts with the operating system and its thread ## Node.js 22.9.0 (Current) DevFeed: [Node.js 22.9.0 (Current)]() Original publisher: [Read original article]() Published: 2024-09-17T21:09:02Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [releases](), [V8](), [JavaScript]() Tags: [cross-platform](), [javascript](), [node-js](), [open-source](), [releases]() ### AI overview Node.js 22.9.0 is a Current release that adds a module API for retrieving the current execution stack trace, disables Maglev by default because of unresolved V8 12.4 issues, and introduces an API option for trusting intermediate certificates in the CA list. It also includes deprecations, benchmark updates, and fixes. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. ## Node.js 22.8.0 (Current) DevFeed: [Node.js 22.8.0 (Current)]() Original publisher: [Read original article]() Published: 2024-09-03T13:51:48Z Content type: release Language: en Sources: [Node.js Blog]() Topics: [Node.js](), [Caching](), [JavaScript](), [test-coverage](), [V8](), [API]() Tags: [benchmark](), [caching](), [cross-platform](), [javascript](), [node-js](), [open-source](), [release](), [tooling]() ### AI overview Node.js 22.8.0 introduces an API for enabling on-disk code caching for subsequently loaded modules, including ESM support. The release also adds an uncified VM context option, configurable code-coverage thresholds, and several performance, networking, test-runner, build, and dependency updates. ### Source excerpt Node.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts. [Next page]()