NOTE: some content in this wiki applies only to 0.12 and earlier versions. For official documentation on 0.13 and later, seehttp://docs.nwjs.io

Note: following guides only apply to node-webkit >= v0.3.0

In order to show thedevtools button in toolbar, you should edit package.json to make sure your window shows the toolbar:

{"window": {"toolbar":true  }}

Then you can open devtools from thedevtools button (the one on the right of url entry) in the toolbar.

Alternatively, even when this button (or the toolbar as a whole) is not visible, you may open devtools programmatically (calling the NW.js'srequire('nw.gui').Window.get().showDevTools() method from one of your scripts).Note: On NW.js 0.13.0+ the command isnw.Window.get().showDevTools().

Requirement: On Windows and Linux, you need to make surenw.pak is in the same directory withnw (Linux) ornw.exe (Windows).

You can use the--remote-debugging-port=port command parameter to specify which port the devtools should listen to. For example, by runningnw --remote-debugging-port=9222, you can openhttp://localhost:9222/ to visit the debugger remotely.

Currently not everything of developer tools is working well, below are the things that don't work:

• node modules don't show in script sources

First off, ensure you are using theSDK version of NW.js. TheNormal version can still launch the Chromium developer tools window, however it will be empty.

Under certain network settings, it may show a white page for devtools. This might not be a bug of node-webkit, devtools in node-webkit is indeed a remote debugger, it needs to open a local server and transfer data via sockets.

So if you encounter empty window when opening the devtools, please check following things:

• nw.pak should be in the same directory withnw.exe.
• Your proxy settings: bypass localhost in the settings.