Description of problem:
When I run nodemon without parameters i'd expect to see instructions on how to get help and be able to use help. This works in upstream version of nodemon just fine.

Version-Release number of selected component (if applicable):
nodejs010-nodejs-nodemon-1.8.1-3.el6.noarch
nodejs010-2.1-5.el6.x86_64

Actual results:
# scl enable nodejs010 'npm list -g nodemon'
npm WARN unmet dependency /opt/rh/nodejs010/root/usr/lib/node_modules/chokidar requires inherits@'^2.0.1' but will load
npm WARN unmet dependency /opt/rh/nodejs010/root/usr/lib/node_modules/inherits,
npm WARN unmet dependency which is version 2.0.0
/opt/rh/nodejs010/root/usr/lib
└── nodemon.1 

# scl enable nodejs010 'nodemon.js'
"usage" help can't be found
# scl enable nodejs010 'nodemon.js --help'
"help" help can't be found


Expected results (upstream):
$ bin/npm list -g nodemon
/home/mhradile/apps/node-v4.2.4-linux-x64/lib
└── nodemon.1

$ bin/nodemon 
  Usage: nodemon [nodemon options] [script.js] [args]

  See "nodemon --help" for more.

$ bin/nodemon --help
  Usage: nodemon [options] [script.js] [args]

  Options:

  -e, --ext ................ extensions to look for, ie. js,jade,hbs.
8><----
  For more details see http://github.com/remy/nodemon/

Additional info:

Just guessing. Could this be something about relative paths being hardcoded?

# cat /opt/rh/nodejs010/root/usr/bin/nodemon.js
#!/usr/bin/env node
'use strict';
var cli = require('../lib/cli');
var nodemon = require('../lib/');
var options = cli.parse(process.argv);

nodemon(options);
8><----