NW.js v0.17.1 Released with Today's Chromium 53 update

Roger Wang

unread,

Sep 8, 2016, 6:08:58 PM9/8/16

to nwjs-g...@googlegroups.com

NW.js 0.17.1 is here with today's Chromium stable 53 update and bug fixes.

Following our release plan in 2016, we have released new major versions as soon as new Chromium stable release within 1 day. We've been working on 3 branches simultaneously: a released branch on current Chromium stable, a beta branch on Chromium beta and a LTS branch which will be supported for the next 2 years.

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 53.0.2785.101
Fix: Failed to load node library (liblibnode.dylib) on child_process.fork (#5269)
Fix: ia32 package file name (#5258)
Fix: typos in common.gypi to prevent nw-gyp failure
[docs] new ffmpeg dll build docs for GN (#5263)

Full changelog: https://github.com/nwjs/nw.js/blob/nw17/CHANGELOG.md

Download

SDK build:

Binaries for other platforms: https://dl.nwjs.io/v0.17.1/

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

VoidVolker

unread,

Sep 9, 2016, 4:37:57 AM9/9/16

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

Thanks, Roger!

In this version bug with 'new-win-policy', when it woks just once, is still present: https://github.com/nwjs/nw.js/issues/2926

Adam Lynch

unread,

Sep 12, 2016, 7:46:16 AM9/12/16

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

The 0.13 link seems to broken so here it is: http://nwjs.io/blog/whats-new-in-0.13/.

Roger, it's great to see NW.js keep up with Chromium so well. Great job. When it didn't keep up as well in the past, some people said this was because of how NW.js patched into Chromium and it took a lot of effort to integrate into each new Chromium release (in comparison to Electon anyway). Is this incorrect and is it simply that the project is running better? Or is it correct and you've somehow worked around that problem? (Like changing how it integrates).

Roger Wang

unread,

Sep 12, 2016, 10:01:45 PM9/12/16

to Adam Lynch, nw.js

On Mon, Sep 12, 2016 at 7:46 PM Adam Lynch <adamly...@gmail.com> wrote:

The 0.13 link seems to broken so here it is: http://nwjs.io/blog/whats-new-in-0.13/.

Roger, it's great to see NW.js keep up with Chromium so well. Great job. When it didn't keep up as well in the past, some people said this was because of how NW.js patched into Chromium and it took a lot of effort to integrate into each new Chromium release (in comparison to Electon anyway). Is this incorrect and is it simply that the project is running better? Or is it correct and you've somehow worked around that problem? (Like changing how it integrates).

As the project being developed we found that keeping up with Chromium upstream is critical for the users to:

* keep updated with latest security fix in time, especially for apps like browser and anyone who displays 3rd party contents from Web.

* use latest features in Chromium

* benefit from latest memory and performance improvements in Chromium. e.g. we have a user depending heavily on the WebRTC feature. By updating to NW with latest Chromium, they upgraded to VP9 codec and saved ~30-40% bandwidth, as well as many CPU cycles. This helped them to fix an important issue onsite with their customers.

* developing side by side with both NW and the Chrome browser with the same version.

So in the end of 2015 when we made plan for this year, it is necessary to make releases in 1-2 days after upstream announce their updates. And I'm glad to see that we executed it well in the past 6 months with Chromium 49-53. All of them are released within 24 hours after upstream release.

The way of how we integrates Node and Chromium has been working well and is not changed. I don't think the statements from Electron guys about our technical details are true. See more information here: https://github.com/electron/electron/issues/5172#issuecomment-210697670

Thanks,

Roger

Adam Lynch

unread,

Sep 18, 2016, 1:29:45 PM9/18/16

to nw.js, adamly...@gmail.com, ro...@nwjs.io

Thanks for all of that, Roger. It clears up a few things for me. The Electron fork discussion is interesting :)

Reply all

Reply to author

Forward