Skip to content

lib: do not add stack traces to `DOMException` instances

Rodrigo Muino Tomonari requested to merge github/fork/aduh95/no-stack-trace-domexception into main

To align with the web. (DOMException are usually created internally anyway, making stack traces mostly irrelevant to end users).

Chromium and Firefox show no stack trace at all:

DOMException: The user aborted a request.

Safari shows only one line that says (anonymous function) (even though there's no anonymous function in user code):

AbortError: Fetch is aborted
(anonymous function)

I suppose a fix would be to ensure our DOMException implementation have no stack property to align with browsers.

Originally posted by @aduh95 in https://github.com/nodejs/node/issues/44253#issuecomment-1218560544

Merge request reports