Skip to content
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

Towards stage 4 #512

Closed
ReinsBrain opened this issue Jul 26, 2023 · 14 comments
Closed

Towards stage 4 #512

ReinsBrain opened this issue Jul 26, 2023 · 14 comments

Comments

@ReinsBrain
Copy link

Hi, I noticed the proposal made it to stage 3 a ways back in March 2022 and hoping to know if stage 4 might be imminent or if there are blockers.

@pzuraq
Copy link
Collaborator

pzuraq commented Jul 26, 2023

Hey! So there is some cleanup I need to do with the spec, there are some minor errors and it needs to be rebased. However, those aren't really blockers at the moment which Is why I haven't prioritized them (I've been swamped at my current job). The main thing we need now is 2 independent implementations in actual browsers, the feature needs to be fully implemented before we can move to stage 4.

I believe the browser teams are currently working on implementing decorators, I will see if I can reach out for updates soon.

@dminor
Copy link

dminor commented Jul 27, 2023

The Firefox implementation is in progress, see https://bugzilla.mozilla.org/show_bug.cgi?id=1781212.

@conartist6
Copy link

Is there a second browser working on an implementation?

@conartist6
Copy link

I see that Deno supports decorators already, since Typescript supports stage three decorators (since TS5.0) and Deno transpiles Typescript. I did find a bug in their implementation though: the decorator transpilation is incorrect when the transpiled class is anonymous.

@nicolo-ribaudo
Copy link
Member

Note that Deno does not transpile .js files, so their implementation should not be considered complete. Also, Deno does not classify a browser for this purposes (given that is uses V8, it's equivalent to Chrome).

@what1s1ove
Copy link

I see that Deno supports decorators already, since Typescript supports stage three decorators (since TS5.0) and Deno transpiles Typescript. I did find a bug in their implementation though: the decorator transpilation is incorrect when the transpiled class is anonymous.

They said that they did not support it with TS 5.0 release.

Take note that ES decorators are not yet supported, but we will be working towards enabling them by default in a future version.

https://deno.com/blog/v1.32

@ReinsBrain
Copy link
Author

With the start of the new year I decided to check back in and am impressed with progress by @dminor and team at firefox : https://bugzilla.mozilla.org/show_bug.cgi?id=1781212

Looks like they are getting close. @pzuraq - any news about other implementers to track?

@pzuraq
Copy link
Collaborator

pzuraq commented Jan 8, 2024

I haven’t heard any updates yet, will post here as I do! I’ve been pretty swamped this holiday season, so unfortunately have not had much time to spend on Decorators, but will be getting back to it in the next month or so.

@jcayzac
Copy link

jcayzac commented Jan 26, 2024

@pzuraq

Chromium bug: https://bugs.chromium.org/p/v8/issues/detail?id=12763

@jcayzac
Copy link

jcayzac commented Jan 26, 2024

@what1s1ove

They said that they did not support it with TS 5.0 release.

From what I remember it was in TS 5.2 release.

@what1s1ove
Copy link

@what1s1ove

They said that they did not support it with TS 5.0 release.

From what I remember it was in TS 5.2 release.

Hey @jcayzac !
The decorators feature was part of TypeScript 5.0 and the decorators metadata feature was a part of TypeScript 5.2.

But this is no longer important, because a few days ago Deno 1.40 was released, where support for the decorators feature appeared.

@pzuraq
Copy link
Collaborator

pzuraq commented Feb 2, 2024

This is a bit of a duplicate of #476 so I'm going to close it, we can continue to discuss implementation status over there

@pzuraq pzuraq closed this as completed Feb 2, 2024
@conartist6
Copy link

It feels rather unfortunate that github can't close issues as duplicates, since now you're saying that stage 4 has been completed and I just double checked and it has not been

@pzuraq pzuraq closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
@pzuraq
Copy link
Collaborator

pzuraq commented Feb 2, 2024

Ah, sorry about that! Seems like there's a way to do that so I'll keep that in mind in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants