doc: clarify V8 option stability in --v8-options docs#62373
doc: clarify V8 option stability in --v8-options docs#62373lilianakatrina684-a11y wants to merge 1 commit intonodejs:mainfrom
Conversation
| not consistent with the system configuration that the users have for some reason. | ||
|
|
||
| ### `--v8-options` | ||
| ### --v8-options |
There was a problem hiding this comment.
Why were the backticks removed?
They consistently are set everywhere else
jasnell
left a comment
There was a problem hiding this comment.
This is already covered in the doc: https://nodejs.org/docs/latest/api/cli.html#useful-v8-options
V8 has its own set of CLI options. Any V8 CLI option that is provided to node will be passed on to V8 to handle. V8's options have no stability guarantee. The V8 team themselves don't consider them to be part of their formal API, and reserve the right to change them at any time
|
Closing this because the existing CLI docs already cover the V8 stability note that this PR tried to add. I will avoid duplicating that wording. |
|
Closing per review: the CLI docs already state that V8 options have no stability guarantee, so this addition would duplicate existing guidance. |
Summary
--v8-optionsdocs that V8 flags are outside Node.js stability guaranteesCloses #62341