06:16 | <Boshen Chen> | Hi all, I'm currently doing some research on what to implement for decorators in Oxc, according to https://github.com/tc39/proposal-decorators?tab=readme-ov-file#how-does-this-proposal-compare-to-other-versions-of-decorators, are we kind of stuck of having to implement both legacy and stage 3 for the ecosystem? |
06:22 | <Boshen Chen> |
I'm also feeling lost on which conformance suite to follow from different implementations, would be great if it is converged to test262. |
08:54 | <nicolo-ribaudo> | There is a wip PR at https://github.com/tc39/test262/pull/4103 for tests |
13:20 | <pzuraq> | Yes, I have been recovering from a surgery so haven’t had a lot of spare time but hoping to land it during the holidays |
13:20 | <pzuraq> | It should run locally on that branch |
13:20 | <pzuraq> | Need to rebase |
14:19 | <Mathieu Hofman> | Hi all, I'm currently doing some research on what to implement for decorators in Oxc, according to https://github.com/tc39/proposal-decorators?tab=readme-ov-file#how-does-this-proposal-compare-to-other-versions-of-decorators, are we kind of stuck of having to implement both legacy and stage 3 for the ecosystem? |
14:20 | <Mathieu Hofman> | IMO we shouldn't encourage usage of the legacy decorators by adding support to new tools |
14:22 | <pzuraq> | Agreed personally |
14:34 | <Boshen Chen> | People always bring up nest.js for this question. https://github.com/nestjs/nest/issues/11414#issuecomment-1495794076 |
14:35 | <pzuraq> | Existing libraries that have had decorators for some time will have to support both for a period, because transitioning existing codebases is going to take a while |
14:35 | <pzuraq> | People have written custom decorators, and they may be using several libs that have varying levels of support |
14:36 | <pzuraq> | But if you’re writing a new lib or framework and you don’t care about interop, I would not add support for legacy |
14:37 | <pzuraq> | Boshen Chen: does Oxc already have decorators? |
14:37 | <Boshen Chen> | The project I'm on is Oxc, which is a js / ts tranpiler :-( |
14:37 | <pzuraq> | Ahh |
14:37 | <pzuraq> | Hmm |
14:38 | <pzuraq> | So, I guess, 1) who is your target demographic, do you really want Nest users to be able to use it? And 2) does it look like that demographic will be moving forward soon? |
14:39 | <pzuraq> | I think I’d start with supporting the new standard and working with major libs to implement support, then if necessary implementing legacy (but only if you can’t get others to update) |
14:39 | <Boshen Chen> | I can defer implementing legacy. Would love to conform to test262 instead of ts / esbuild / babel's suite when we start implementing :-) |
14:40 | <pzuraq> | Nice! Yeah I’m tied up for the next couple weeks but like I said, I want to get the tests merged sooner rather than later |
14:41 | <pzuraq> | If you wanna help out with my PR, like rebasing it and getting any comments handled, that would definitely help |
14:42 | <Boshen Chen> | I may not be the implementor, but I'll pass that PR to the implementor when they start. |
14:45 | <pzuraq> | Cool, they can ping me on here or via email |
14:46 | <pzuraq> | Me@pzuraq.com |