NW.js v0.106.0 Released with Chromium 143, Win ARM64 and Node.js v25

33 views
Skip to first unread message

Roger Wang

unread,
Nov 23, 2025, 7:56:30 PMNov 23
to nw.js

I'm pleased to announce NW 0.106.0 with Chromium 143. Node.js is updated to v25, and Win ARM64 build is supported.

In NW v0.106, Chromium 143 contains usual under-the-hood performance and stability tweaks, but there are also some cool new features to explore. It supports more characters in JavaScript DOM APIs, CSS anchored fallback container queries and much more. Please check upstream release notes for details. For a complete list of all features (including experimental features) in this release, see the Chrome 143 milestone hotlist.

I've made the 0.106 branch ready soon after Chromium beta bumps to 143. Thanks to the testers for their valuable feedback and bug reports. I've been working on 2 branches simultaneously: a released branch on the current Chromium stable and a beta branch on Chromium beta.

Best regards,
Roger Wang

ChangeLog

  • Update to Chromium 143.0.7499.40
  • Node: update to v25.1.0

Full ChangeLog: https://github.com/nwjs/nw.js/blob/main/CHANGELOG.md

Download

SDK build:

Binary for other platforms: https://dl.nwjs.io/v0.106.0/

There are 2 builds for each platform - normal build, and SDK build. Normal build doesn't have devtools, only SDK build does. lt can be opened by pressing F12 (Cmd-Alt-I on OSX). SDK packages also have more development tools to be exposed in the following releases, as well as the NaCl support.

Our build infrastructure enables live binary build from git tip so you can access to the latest binary from https://dl.nwjs.io/live-build/

Benoit Schmitlin

unread,
Dec 8, 2025, 4:56:09 PM (10 days ago) Dec 8
to nw.js
Hi, 

with 106 I'm wondering how I should deal with the "Uncaught TypeError: localStorage.getItem is not a function" error that props up since the node 25 upgrade, probably due to a conflict between the new node API and the browser localStorage. How have people dealt with it? Or is that something that needs to be fixed in nw.js? 

thanks.

Reply all
Reply to author
Forward
0 new messages