NW.js v0.19.0 Released with Chromium 55 and async/await functions

[Roger Wang]

We're pleased to release NW.js 0.19.0 with today's Chromium 55 stable upgrade.

Chromium 55 contains under-the-hood performance and stability tweaks, and some cool new features to explore like input handling improvements. See the upstream announcement for more information. NW19 also features V8 5.5, which ships support for JavaScript's async/await & has 35% less memory consumption on low-memory devices.

There are many security fixes in this release, e.g:

• High CVE-2016-9651: Private property access in V8.
• High CVE-2016-5208: Universal XSS in Blink.
• High CVE-2016-5207: Universal XSS in Blink.

We've made the 0.19 branch ready soon after Chromium beta bumps to 55. Thanks to the beta testers for their valuable feedback.

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 since v0.18.8

• Update Chromium to 55.0.2883.75
• Fix: 'show_in_taskbar' option for 'nw.Window.open' (#4970)
• Fix: process.uptime() (#5481)

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

Download

• https://dl.nwjs.io/v0.19.0/nwjs-v0.19.0-win-x64.zip
• https://dl.nwjs.io/v0.19.0/nwjs-v0.19.0-osx-x64.zip
• https://dl.nwjs.io/v0.19.0/nwjs-v0.19.0-linux-x64.tar.gz

SDK build:

• https://dl.nwjs.io/v0.19.0/nwjs-sdk-v0.19.0-win-x64.zip
• https://dl.nwjs.io/v0.19.0/nwjs-sdk-v0.19.0-osx-x64.zip
• https://dl.nwjs.io/v0.19.0/nwjs-sdk-v0.19.0-linux-x64.tar.gz

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

[mike.k...@gmail.com]

Hi Roger,

Which stable release will become the next LTS release (after 0.14.x)? Also, How long are updates from upstream Chromium/Node backported to a given stable version? 

Thanks

[Roger Wang]

In the LTS announcement, it's noted that Chromium and Node will not be upgraded to support legacy Windows and OSX systems. Our suggestion is that please don't use LTS unless you're going to support Windows XP/Vista or OSX 10.6-10.9.

We have been planning to make another announcement to rename the LTS release, because the name is misleading. As Chromium and Node is not receiving updates in this branch, many security issues are not fixed. And we won't backport those many patches to the 0.14 branch due to deep dependencies. So application developers should keep their software updated with the latest Stable, especially when they are dealing with 3rd party contents from Internet.

In order to deliver secure software, we made the release plan that keeps updated with upstream closely. We release a major version in 1-2 days after Chromium stable is upgraded to a new version. And every new release of Chromium comes with many security fixes: https://googlechromereleases.blogspot.com/search/label/Stable%20updates

Based on this consideration we tend not to support another branch based on an outdated version of Chromium(and Node).

Thanks,

Roger

--
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.

[pp w]

I want to build nw19 but failed

I took a look at http://docs.nwjs.io/en/latest/For%20Developers/Building%20NW.js/ and built nw17 successfully.

Why can not i build nw19？

Thanks

在 2016年12月5日星期一 UTC+8上午9:24:20，Roger Wang写道：

[rucka...@gmail.com]

For me this is working:

./build/gyp_chromium -D component=shared_library -I ./third_party/node/common.gypi ./third_party/node/node.gyp

Not very clear how it works from the documentation. I myself have problem with debug build. Not able to link node (on win 7) because of mismatch between release and debug build (although everything (including nw) is build as debug). Not sure if it is worth of my time to try to resolve it somehow. Any advice?

[Roger]

The documentation is updated now. Thanks.

Roger

[Ed Thompson]

Releasing a commercial app on 0.19.0 next week - crossing my fingers ;)

[rucka...@gmail.com]

Well done Roger.

Did you ever tried debug build under Windows? Normal build contains a lot of debug symbols, but debug build is always better. I build nw as debug (is_debug=true) without problem. But then I wasn’t able to build node. I generated node files with:

 

python build/gyp_chromium -Dtarget_arch=ia32 -I third_party/node/common.gypi third_party/node/node.gyp

I tried it with is_debug switch as well (but I think it’s no difference)

python build/gyp_chromium -Dtarget_arch=ia32 -Dis_debug=true -I third_party/node/common.gypi third_party/node/node.gyp

 

After this I normally build it with:

ninja -C out/Debug node

or even

ninja -C out/Release node

But I always got LINK errors:

v8_libplatform.lib(default-platform.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in node.debug-agent.obj

and I am not sure how to set everything right. Obviously some part is set as release and some as debug... How should I do it?

[Roger]

Component build should be used when build debug version. That's the requirement from upstream IIRC. Will add this to doc.

Roger

[Roger]

https://groups.google.com/a/chromium.org/d/msg/chromium-dev/LWRR3fMlvQ4/qos4EaBtBgAJ

[rucka...@gmail.com]

Thanks, At last I was able to run debug build. nwjs with is_debug=true flag.I was build as component even without appropriate flag and node with:

python build/gyp_chromium -Dtarget_arch=ia32 -Dcomponent=shared_library -I third_party/node/common.gypi third_party/node/node.gyp