module.parent not null when run from npm-register.cmd

[cdibbs]

The server will not start under windows after global installation. Poking around, it's due to module.parent:

if (!module.parent) {
  app.listen(app.port, function () {
    console.error(`${app.name} listening on port ${app.port} [${app.env}]`)
  })
}

When you install under windows, you get a npm-register.cmd which then runs npm-register\bin\npm-register, which becomes the parent. I was able to get it working by skipping all that and running node path/to/start.js start. That works for me, for now.

Here's a dump of module.parent, in case its useful:

Module {
  id: '.',
  exports: {},
  parent: null,
  filename: 'C:\\Program Files\\nodejs\\node_modules\\npm-register\\bin\\npm-reg
ister',
  loaded: false,
  children:
   [ Module {
       id: 'C:\\Program Files\\nodejs\\node_modules\\npm-register\\node_modules\
\yargs\\index.js',
       exports: [Object],
       parent: [Circular],
       filename: 'C:\\Program Files\\nodejs\\node_modules\\npm-register\\node_mo
dules\\yargs\\index.js',
       loaded: true,
       children: [Object],
       paths: [Object] },
     Module {
       id: 'C:\\Program Files\\nodejs\\node_modules\\npm-register\\server.js',
       exports: [Object],
       parent: [Circular],
       filename: 'C:\\Program Files\\nodejs\\node_modules\\npm-register\\server.
js',
       loaded: false,
       children: [Object],
       paths: [Object] } ],
  paths:
   [ 'C:\\Program Files\\nodejs\\node_modules\\npm-register\\bin\\node_modules',

     'C:\\Program Files\\nodejs\\node_modules\\npm-register\\node_modules',
     'C:\\Program Files\\nodejs\\node_modules',
     'C:\\Program Files\\node_modules',
     'C:\\node_modules' ] }

[madaz]

Same problem on Windows 10, to start I use the the following cmd line
node C:\Users\[UserName]\AppData\Roaming\npm\node_modules\npm-register\server.js

[dgautsch]

Windows compatibility was recently added with #92 in v2.8.0