Jake Bailey
Jake Bailey
For those following this issue, #51387 will fix this (though it was later than 4.6 😄).
@typescript-bot test this @typescript-bot test top100 @typescript-bot user test this @typescript-bot user test tsserver @typescript-bot test tsserver top100 @typescript-bot run dt @typescript-bot perf test this @typescript-bot pack this
It does! Thanks.
Interesting break, I'll look into it. Note that since main has changed, this PR is now broken again (as expected); I won't be able to run any new tasks on...
Apparently it's not my break, and is happening elsewhere: #51218 Phew!
> Regrettably at present custom Azure Pipeline tasks that are built in TypeScript are run with either https://github.com/microsoft/azure-pipelines-agent/issues/3195. Yes, the whole "could we be ESM?" thing is what prompted Daniel's...
Thanks for the clarification! I don't think emit for those old targets is going away any time soon (per #51000), so this is good news for me.
I updated the PR description to mention this, but if you are interested in looking at this PR without being totally overwhelmed by the size of the diff, I would...
It does, yes, but we have two ways around that: - Wait to use newer features. We already basically do this so we can run ESLint on the codebase. -...
> Would it make sense to add a tool that could do that before publishing? it's unfortunate that esbuild doesn't offer any settings for this... I saw that comment too,...