For AI agents: the complete documentation index is available at /tc39-atlas/en/llms.txt, the full documentation bundle is available at /tc39-atlas/en/llms-full.txt, and this page is available as Markdown at /tc39-atlas/en/proposals/year/pending/proposal-error-stacks.md.
TC39 Atlas
  • English

      • Error stacks S1

      Proposal details
      Proposal overview

      The proposal standardizes the de facto Error.prototype.stack property, addressing security concerns around improper standardization. It catalogs existing implementations across V8, Safari, and Firefox, and proposes an Annex B specification.

      Note

      The README below comes from the upstream repository and may contain outdated stage or status metadata. Use the proposal details above as the current source of truth.

      Error Stacks

      ECMAScript Proposal, specs, and reference implementation for Error.prototype.stack/System.getStack/System.getStackString

      Spec drafted by @ljharb along with @erights.

      This proposal is currently stage 1 of the process.

      Rationale

      Errors have never had a stack trace attached in the language spec — however, implementations have very consistently provided one on a property named “stack” on instantiated Error objects. There has long been concern about standardizing stack traces improperly - such that implementations could not claim to be fully compliant while also providing security guarantees. This proposal is an attempt to standardize the intersection of existing browser behavior, in a way that addresses these security concerns.

      Compatibility

      Object.getOwnPropertyDescriptor(new Error(), 'stack');
Object.getOwnPropertyDescriptor(Error.prototype, 'stack');

      V8 in Node 7-20 and Chrome 54-114: stack is an own property on Error instances which claims to be a value property ({"value":"(stack here)","writable":true,"enumerable":false,"configurable":true), but V8's Error has exotic behavior for [[GetOwnProperty]] that acts like a getter the first time (if there's been no set first) by triggering prepareStackTrace and setting stack, as discussed in this thread. After that, it behaves like a standard value property.

      V8 in Node <= 6 and Chrome <= 53, and Node >= 21 and Chrome >= 115: stack is an own property on Error instances with a getter/setter: { configurable: true, enumerable: false }

      • The getter returns undefined with a non-Error receiver, and returns the stack property (whatever its current value may be) otherwise.
      • The setter is a no-op with a non-Error object receiver, and sets the return of the stack getter otherwise.

      Safari: stack is an own string data property on Error instances: { configurable: true, enumerable: false, writable: true }

      Firefox: stack is an own property on Error.prototype: { configurable: true, enumerable: false }

      • The getter throws on a non-Error receiver, and returns the original stack trace otherwise.
      • The setter sets the stack property on a non-Error receiver, and is a no-op on an Error receiver.

      Naming

      Error.prototype.stack is set in stone - this is a defacto reality, and will be implemented in Annex B.

      Spec

      You can view the spec rendered as HTML.