Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
wiktorn opened this issue May 27, 2021 · 1 comment
Open

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

wiktorn opened this issue May 27, 2021 · 1 comment

Comments

@wiktorn
Copy link

wiktorn commented May 27, 2021

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
Copy link

ZzZombo commented Apr 29, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants