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.
Full changelog: https://github.com/nwjs/nw.js/blob/nw17/CHANGELOG.md
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/
http://docs.nwjs.io/en/latest/For%20Users/Migration/From%200.12%20to%200.13/#known-issues
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).