Repository navigation
Different ways to allow V8 options in NODE_OPTIONS? #46339
Description
Refs: #46203
We should probably formulate a strategy on NODE_OPTIONS vis-a-vis V8 options because there are tons of them. Adding them haphazardly is, let's say, suboptimal.
Right now what we do is simply adding no-op options for these to our own option parser with kAllowedInEnvvar and pass them down to V8 to make them available to NODE_OPTIONS. We might want a different approach for that.
Activity
juanarbol commentedon Feb 12, 2023
I don't see the available options of V8 being exposed; I could work on a "getter" for those. See https://source.chromium.org/chromium/chromium/src/+/main:v8/src/api/api.cc;l=802?q=SetFlagsFromCommandLine&ss=chromium%2Fchromium%2Fsrc, like expose
v8_flagsin the V8 API; or maybe theprintHelp()method, grab that output and parse it in the Node.js side.juanarbol commentedon Feb 15, 2023
I'm working on a PoC for this :)
juanarbol commentedon Mar 13, 2023
I'm dealing with some errors, but from the V8 side, I got a way to get the flags.
I was considering creating a macro that runs the
AddOptionfunction or something like that. In the meantime, I will debug why flags are becoming random chars, but usingprintfusually works.github-actions commentedon Jun 22, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 23, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.