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

Add options for bypassing various translations #15

Open
zenparsing opened this issue Feb 17, 2015 · 8 comments
Open

Add options for bypassing various translations #15

zenparsing opened this issue Feb 17, 2015 · 8 comments

Comments

@zenparsing
Copy link
Owner

This would be useful for bypassing block-scope translation when just running ES6 code directly on node/iojs.

@yukulele
Copy link
Contributor

yukulele commented Jul 1, 2015

👍

@gr0uch
Copy link

gr0uch commented Sep 4, 2015

👍 very interested in this feature.

@zenparsing
Copy link
Owner Author

@yukulele @0x8890 How would you like to see this feature exposed?

We could have flags for each individual translation feature, or we could could have some kind of "target" argument, that would be smart about what a particular target supports.

@gr0uch
Copy link

gr0uch commented Sep 4, 2015

I think that flags for individual features would be good. Build targets would be kind of a pain to maintain, though it would be more convenient.

@yukulele
Copy link
Contributor

yukulele commented Sep 9, 2015

agree with @0x8890

@gr0uch
Copy link

gr0uch commented Sep 15, 2015

I just wanted to add that for Node v4.0 (or recent chromium/chrome), the only things that I would care about transpiling:

  • default function parameters
  • es6 module syntax
  • destructuring assignment
  • spread operator
  • class syntax (currently supported in strict mode)

@zenparsing
Copy link
Owner Author

@0x8890 Node v4 supports classes in strict mode (and ES6 modules are always strict mode), and everything else except modules is currently being developed for V8.

https://www.chromestatus.com/features#category: JavaScript

@gr0uch
Copy link

gr0uch commented Sep 15, 2015

oops, I read this compatibility table and just assumed that it was hiding behind a flag.

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

3 participants