There are various open issues in node-webkit's github page regarging problems with stdin, stdout, stderr and argv. This module wraps nw to work arroung this issues.

There are two parts to it. node_modules/.bin/nw-wrap is what you execute as the parent process:

npm install nw-wrap
node_modules/.bin/nw-wrap args to node webkit and your app

Or, better yet, add it as a script in your package.json

"scripts": { "start": "nw-wrap args to node webkit and your app" }

and run it with npm start.

The other part, main.js, is what you get when you require('nw-wrap') from inside your appliaction. It returns an extended process object, with process.stdin connected to the nw-wrap executable's process.stdin via TCP.

nwwr = require('nw-wrap');
nwwr.stdin.pipe(nwwr.stdout);

For stdout and stderr the default behaviour is to pipe them to the parent process, but if stdout isn't working for you, or you want to clear up stderr for your own use, you can set the STDOUT_PORT, STDERR_PORT environment variables, and nw-wrap will connect the respective stream over TCP to the nw-wrap executable's corresponding standard stream.

For example, on linux stdout works just fine, but you might want to silence nw's stderr:

STDERR_PORT=7869 nw-wrap args to node webkit and your app

Overriding the global.process with the return value of require('nw-wrap') breaks things, I don't know why. Doing so is probably a bad idea anyway. At first I did this so I could have a cli options parser like yargs pick process.argv up correctly. Fortunately, that's not necessary, since you can feed yargs any object, so I just pass it nwwr.argv.

MIT