Skip to content

Commit 484ee1b

Browse files
authored
Update README.md
1 parent 4046922 commit 484ee1b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Error.captureStackTrace
22

3-
**Stage**: [Stage 0](https://tc39.es/process-document/)
3+
**Stage**: [Stage 1](https://tc39.es/process-document/)
44

55
**Champion**: Matthew Gaudet (Mozilla)
66

@@ -48,3 +48,6 @@ I would actually like to specify this like the JSC one. It's simpler. Similarly,
4848

4949
- The [Error Stacks](https://github.com/mgaudet/proposal-error-capturestacktrace) proposal is largely an orthogonal one to this, but it would provide framework and text to talk about stack strings, as mostly the current spec doesn't really talk about stacks. However, for this proposal I'd argue we don't need to specify the contents of stack strings.
5050
- The [Error Stack Accessor](https://github.com/ljharb/proposal-error-stack-accessor/) proposal could be the other route by which the spec starts to talk about stacks.
51+
52+
## History
53+
- Presented February 2025, and achieved Stage 1 [(slides)](https://docs.google.com/presentation/d/1SFdS9n5JR7Jqz29s7ApvkqDOqOfPW-IaBR2orK828As/mobilepresent?slide=id.p) (notes not yet posted)

0 commit comments

Comments
 (0)