-
Notifications
You must be signed in to change notification settings - Fork 3.9k
NW.js 0.13.0 Migration Notes
Cong Liu edited this page Dec 1, 2015
·
4 revisions
This page is subject to change during the development of NW.js 0.13.x
-
require('nw.gui')
does NOT exist. Instead, you can directly access NW.js API vianw.*
. - Global Node.js objects, such as
require
,process
,Buffer
etc., do NOT exist. All Node.js objects are now loaded innw.*
. Just usenw.require('http')
to require Node.js modules. - If NW.js is running under Mixed Context mode (boot NW.js with
--mixed-context
argument),nw.*
is kind of mirror ofwindow.*
. In this mode, you CANNOT share variables among frames or windows by assigning it to Node context. So do NOT turn on Mixed Context mode if your application is heavily depending on this variable sharing feature.
- Node.js is bumped to 5.x in latest build. Check your NPM modules to make sure they support Node.js 5.x. If you have dependencies of native modules, check on this list to see whether you have a compatible version.
- Different build flavors support different set of APIs and capabilities. See Build Flavors to choose the right NW.js flavor or [build your own](Building nw.js).
-
Shortcut
API does NOT map Ctrl modifier to ⌘ on Mac OS X. However 0.13.0 supportsCommand
modifier in cross platform way. So it's your responsible to detect the OS and choose the right modifier when registering hotkeys. See Shortcut.
TBD