Evan Wallace

Hey, thanks for the bump. There's no reason to not get this in. I think something like this makes sense and I'm supportive of it. The only reason it hasn't...

There are several approaches to this. In general `RunWith*` functions are not a great approach to extending APIs with many optional parameters, as there could be a combinatorial explosion of...

The [decorator spec](https://github.com/tc39/proposal-decorators) unfortunately still seems like it's a long way off, both based on low activity and based on how many things it looks like they still have to...

An initial implementation of TypeScript decorators has been released in version 0.4.10. You can read more about this in [the release notes](https://github.com/evanw/esbuild/blob/master/CHANGELOG.md#0410). Please let me know if you encounter any...

Decorators are not a JS feature, so esbuild doesn't support them in JS. Nothing in the JS specification mentions decorators: https://262.ecma-international.org/12.0/. But they are a TS feature, so esbuild supports...

My plans are to implement it after it has shipped in a browser, in node, or in TypeScript. This is the same thing that I do for all other syntax...

I looked into this in more detail and it seems like TypeScript is only doing a partial implementation. Work on the specification is ongoing and the API is likely going...

It looks like the specification is still actively being iterated on. For example: https://github.com/tc39/proposal-decorators/issues/499. I can reopen this issue if you want, but I still don't think it's the right...

Yes, I'm planning to do this. That's one of the main reasons why I did the work behind #3019. Previously esbuild considered all decorators in TypeScript files to be experimental...

[Version 0.18.5](https://github.com/evanw/esbuild/releases/tag/v0.18.5) of esbuild now supports parsing and printing JavaScript decorators, and parsing and transforming auto-accessors. Please try out these features and let me know if you encounter any problems.