v8 flag removal: --detailed-error-stack-trace

[dcarney-cf]

Affected URL(s)

No response

Description of the problem

just a head's up --detailed-error-stack-trace is going away.
https://chromium-review.googlesource.com/c/v8/v8/+/7679403
the runtime cost of using that flag even when disabled is too high.

[jasnell]

For those unfamiliar, this is a V8 CLI option that carries no semver guarantees by node.js. I asked Dan to open the issue as a heads up since it's referenced in various materials and documentation in the ecosystem

[lilianakatrina684-a11y]

Opened a docs follow-up in #62373 to clarify in the --v8-options section that V8 flags are outside Node.js stability guarantees and may change or be removed between releases.

[targos]

That seems OK. I have never heard of this flag before and quick Google search shows almost no reference to it.

[jasnell]

Github code search will show it being recommended at times for diagnostics/debugging but it is a pretty obscure one. Can't imagine folks will every actually notice it's gone.

[joyeecheung]

The flag was added for llnode which is now unmaintained. Even if it is revived this shouldn’t be done through a runtime flag but should be done with better uses of the debugger helper library.

[jasnell]

We likely don't need to keep this issue open. It was mostly for a heads up and to see if anyone objected for whatever reason, which it doesn't appear there is.