search

coreybutler / node-windows

Windows support for Node.JS scripts (daemons, eventlog, UAC, etc).
Other
2.83k stars 356 forks source link

nodeOptions passed both to wrapper process as the service process #284

Open wiktorn opened 3 years ago

wiktorn commented 3 years ago

All arguments set in nodeOptions are used to execute the wrapper service and then reused, to call the service itself.

If --inspect or --inspect=<portnum> (where portnum !=0) is provided as nodeOptions it prevents from starting the service, as the wrapper process is already bound to desired port.

My expectations is that nodeOptions should be passed only to the service nodejs process and not at all to wrapper process or at least there should be a way to provide nodeOptions that will be used only by service process and not by wrapper process.

ZzZombo commented 1 year ago

This! Why is that the current behavior is beyond me, it's really flawed. Now I can't even make use of the new Permissions in Node v20.