Allow inspector flags with SEA binaries via configuration

[cmaster11]

What is the problem this feature will solve?

It is currently impossible to enable the debugger at the start in a SEA binary because both CLI flags (like --inspect) and NODE_OPTIONS don't allow it. The only current workaround is sending the SIGUSR1 signal to the program, which can only be achieved when the program starts successfully and has limitations due to the impossibility of specifying the HOST:PORT args.

See:

node/src/node_options.cc

Line 306 in 8a41d9b

if (sea::IsSingleExecutable()) return;

What is the feature you are proposing to solve the problem?

I think it would be nice to have an additional flag in the SEA config that would allow for these options to be enabled. This would allow the distribution of debuggable binaries for any testers involved in a project.

What alternatives have you considered?

The current alternative is to distribute the standalone node binary + a CJS bundle, which is not the same as having a single file UX-wise.

[joyeecheung]

Allowing this in the configuration makes sense to me. Not sure what the reasoning to ignore it initially was - that was before we had the configuration though. Any thoughts? @nodejs/single-executable

[tony-go]

I do not remember precisely, but I remember having a discussion with @RaisinTen this past year.

But it makes sense to me to allow this configuration, too.

[github-actions]

There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Mark issue so that it is never considered stale label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.

[github-actions]

There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.

For more information on how the project manages feature requests, please consult the feature request management document.

[cmaster11]

I feel this feature would be valuable to have, so I'd like to keep the issue open.

…

On Tue, Sep 10, 2024, 04:28 github-actions[bot] ***@***.***> wrote: There has been no activity on this feature request and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment. For more information on how the project manages feature requests, please consult the feature request management document <https://github.com/nodejs/node/blob/HEAD/doc/contributing/feature-request-management.md> . — Reply to this email directly, view it on GitHub <#51688 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2SGJ7CENFG44LNKIJNV6TZVZDMRAVCNFSM6AAAAABC5GMDGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZZGQZTCNRZGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[cmaster11]

This issue could also be solved via #55573 (if it does not deserve its standalone flag) as long as there is a way to bake-in/pass some node options at runtime.