NW.js v0.22.0 Released with Chromium 58 Stable Upgrade

Roger Wang

unread,

Apr 19, 2017, 10:05:19 PM4/19/17

to nwjs-g...@googlegroups.com

We're pleased to announce NW.js 0.22.0 with Chromium 58 Stable Upgrade. In the version, the JavaScript Source Code Protection feature is vastly improved by elimating the performance overhead. See the blog post for more information.

Chromium 58 contains under-the-hood performance and stability tweaks, and some cool new features to explore like IndexedDB 2.0 and an improvement to iframe navigation. See the upstream announcement for more information.

We've made the 0.22 branch ready soon after Chromium beta bumps to 58. Thanks to the testers for their valuable feedback. We've been working on 3 branches simultaneously: a released branch on current Chromium stable, a beta branch on Chromium beta and a 0.14 branch for legacy OS support.

For more information on the new milestone 0.13 and later versions, please see our blog "What's New in 0.13" for a better introduction.

ChangeLog

Update Chromium to 58.0.3029.81
Fix: New window created using window.open not honouring height and width (#5517)

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

Download

SDK build:

Binary for other platforms: https://dl.nwjs.io/v0.22.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/

Known issues

http://docs.nwjs.io/en/latest/For%20Users/Migration/From%200.12%20to%200.13/#known-issues

dahms.ch...@gmail.com

unread,

Apr 21, 2017, 2:32:31 AM4/21/17

to nw.js, ro...@nwjs.io

Great news, Roger!

Is the V8 performance bump enabled by default or do we need the

$ nwjc --future source.js compiled.bin
$ nw --js-flags="--future"?

Roger Wang

unread,

Apr 21, 2017, 7:14:58 AM4/21/17

to dahms.ch...@gmail.com, nw.js, ro...@nwjs.io

The switch is needed in 0.22. In 0.23 it will become the default.

--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

dahms.ch...@gmail.com

unread,

Apr 21, 2017, 9:37:32 AM4/21/17

to nw.js, dahms.ch...@gmail.com, ro...@nwjs.io

Thanks Roger.

I assume using

"js-flags": "--future"

in the package.json works accordingly for starting nwjs normally then?

Reply all

Reply to author

Forward