Today our upstream made an announcement about their plan on Chrome Apps, in which Chrome Apps will not be supported on Win, Linux and macOS.
NW.js can run Chrome Apps directly and we'll continue supporting it. Chrome App developers can redistribute their application after packaging with NW.
Staring from version 0.13, NW.js brings most features in the Chromium browser, including Chrome Apps support, chrome. platform APIs. We support all `chrome.` API in the Chrome App platform. In addition, we support some chrome.* API in the Extension Platform.
Chrome Apps can be run directly on NW. Clone the sample apps repository and run one of them with:
$ /path/to/nw.exe <folder path of the manifest.json file>
or drag the folder to the NW executable. And of course Node.js APIs can be accessed from Chrome App: add “node” permission to manifest.json and you are ready to call nw.require().
For more information, see What's new in 0.13
-webkit-
prefix. Be careful with these non-standard features since they may be deprecated shortly."--
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.
open -n -a nwjs --args /Users/mirzadelic/Projects/caffetouch
in mac, but gcm doesn't work, can't get reg id from chrome.gcm.register api.
Any suggestion?
The gcm API is a special case: try adding --enable-gcm switch.
--
I want to be able to pack and distribute my chrome app.