-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation Status #476
Comments
|
@nicolo-ribaudo Sorry, should've been more clear. I was thinking specifically about the proposal as it's now in stage 3. E.g. |
Have the |
Ok, yes: babel/proposals#81 (comment) |
@nicolo-ribaudo #467 was merged, resolving. |
For the stumblers, stage 3 decorators landed in Babel on Sep 5th: https://babeljs.io/blog/2022/09/05/7.19.0 🎉 Here's a small guide on how to use them in TypeScript: microsoft/TypeScript#48885 (comment) |
It appears the new decorators won't land on TS before 5.0 |
Thanks, updated the overview item to "after 4.9". |
Anyone know if Chrome or Safari have started implementation? |
Chrome seems to be making progress on auto accessors: https://issues.chromium.org/issues/42202709 |
Updated the description with updated status for TypeScript and V8/Chrome. Also made it easier to skim for shipping versions and turned it into a checklist. |
esbuild also includes support for decorators: https://github.com/evanw/esbuild/releases/tag/v0.21.0 and decorator metadata: https://github.com/evanw/esbuild/releases/tag/v0.21.3 |
I checked some of the engine/tool issue trackers and couldn't find any clear signal on what the status of the proposal is when it comes to stage 3 implementations. What I found so far:
Babel is actively working on aligning with the latest revision, see Add 2022-03 decorators version (stage 3) babel/babel#14836.Does that reflect the current status?
The text was updated successfully, but these errors were encountered: