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

decorator with 2.6.0-rc and esnext, tsc still transpiles, no way to turn off transpilation even with esnext #19384

Closed
aappddeevv opened this issue Oct 20, 2017 · 2 comments
Labels
Duplicate An existing issue was already created

Comments

@aappddeevv
Copy link

aappddeevv commented Oct 20, 2017

TypeScript Version: 2.6.0-rc

There is not way to turn off decorator transpilation processing so that it passes through. I use babel for filling and compiling down to my target javascript environment so typically I do not want tsc to transpile modern javascript features. target=esnext helps ensure that tsc assumes that the target environment is quite modern.

However, if there is a decorator in the ts file, it is translated into __decorate(...) regardless of what settings I might use to try and keep it intact into my next compilation stage, which is babel.

@freeze
class Foo { ... }

Even using esnext as the target, you get in the source:

... = __decorate(...)

But we really want pass through like many other features of javascript that pass through when esnext is set:

@freeze
class Foo { ... }
@mhegazy
Copy link
Contributor

mhegazy commented Oct 20, 2017

Duplicate of #16882

@mhegazy mhegazy marked this as a duplicate of #16882 Oct 20, 2017
@mhegazy mhegazy added the Duplicate An existing issue was already created label Oct 20, 2017
@mhegazy
Copy link
Contributor

mhegazy commented Nov 6, 2017

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.

@mhegazy mhegazy closed this as completed Nov 6, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

2 participants