So some may use this if they value smaller dist sizes as well. It will have a much smaller file size compared to newer NW.js versions because Chromium and Node have just gotten much bigger since this release. Should you use this: Only if you need need to support older OS's. Not sure why the LTS version uses Chromium 50 and not 49. Officially Chromium 50 dropped support for XP, Vista, OS X 10.6, 10.7, and 10.8. This is the officially recommended version for legacy OS's. And as far back as Ubuntu 10 (maybe 8, I don't quite remember). This is the 'Long Term Support' (LTS) version of NW.js. Should I use this: No, everything this version offers is better handled in newer versions.

This also spawned the newer website and documentation site focused on 0.13+. It had a newer API that has remained almost completely unchanged since it's release. This was the first stable release of the newer Architecture. It's based on a very old version of Chromium and IO.js (~Node v1), meaning you need to write your code in a pretty outdated manner. Should you use this: No, the API is too different from modern NW.js. It is possible to create an installable executable that is less than 20MB in size on Windows (though expands to ~65-70MB on install). This has the smallest footprint of file size/dist/memory/cpu of any NW.js version. This version shipped with a then compatible Mac App Store version (MAS) and a 'normal' which came with dev tools built in but only accessible by the optional toolbar or programmatically (not by keyboard shortcut unless you set that up yourself). The old wiki on GitHub acted as the source of documentation for this version. It also has an optional toolbar built in and does not ship without devTools. If using 'main': 'index.html' the URL will actually be the file:// filepath, rather than a chromium-extension URL like on newer NW.js versions. However it does have a slightly different approach to handling the window and loading the page. It is no longer recommended by anyone as its API is just different enough to not be worth it (would be harder to upgrade). This was the last version to use the original architecture. NW.js v0.64.1 works with 10.15 and no longer accurately updates the plist file.

NW.js v0.14.7 and below works with 10.6+.OSX Support isn't well documented, but here's what I've heard from the community Yes, use this, unless you need one of the above features Has a bug that prevents loading on Windows 7. Only if you need to do your app development on Windows 7 Introduces Tray app bug that is fixed in 0.48.0 Only if you need to do Tray app development on Win 7 Newer versions offer same performance gains Only if you need to support legacy OS's, use newer version for newer OSs

Nw.js download