Skip to content

Any plans for es6 and traceur support? #684

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

Closed
agnislav opened this issue Nov 6, 2014 · 8 comments
Closed

Any plans for es6 and traceur support? #684

agnislav opened this issue Nov 6, 2014 · 8 comments

Comments

@agnislav
Copy link

agnislav commented Nov 6, 2014

Hi guys,

Is there a plan to include traceur support to the generator? It would be nice to play with ES6 today to be ready for angular 2.0.

Sincerely,

Agnislav.

@Awk34
Copy link
Member

Awk34 commented Nov 8, 2014

Angular 2.0 is waayyy in the future

@agnislav
Copy link
Author

agnislav commented Nov 9, 2014

I'd like to be ready for that sweet moment )

@kirkkohler
Copy link

@Awk34, I think the request was including an ES6 option with Traceur with Angular 1.x. In prep for the eventual ES6 and Angular 2.x releases. Or to just leverage ES6 today.

e.g. Taking the pain out of the config as mentioned in these blog posts.
http://collectivegarbage.azurewebsites.net/builds/
http://eugenioz.blogspot.com/2014/11/angularjs-13-and-es6-how-to-use-it.html

@andrewstuart
Copy link
Member

Oy. I have to say I'm kinda disappointed with a lot of the decisions on Angular 2. If having the most popular modern framework on the web didn't stop them from breaking almost every construct they'd set up, I'm not sure what will.

I'm sure I'll end up using it and getting used to where they're going (feel free to talk me off the ledge), but it get the ominous impression that if I go with Angular 2, I won't really be using full-stack JS anymore. It'll be AtScript on the client, compiled to incomprehensible (barely debuggable) es5 for a while, and then JS on the server.

That said, ES6 does have some features I'm excited about.

@kirkkohler
Copy link

@andrewstuart good points and I've seen a lot of folks who express your same concerns of current plans for Angular 2.

Ignoring Angular 2 for a moment, I think it would be great to add a switch into the fullstack-ang generator to allow opting in/out of using ecmascript 6 with Traceur.

@JaKXz
Copy link
Collaborator

JaKXz commented Mar 5, 2015

It would be cool to leverage Babel and just start using ES 2015 / 2016 features already.

@Awk34
Copy link
Member

Awk34 commented Mar 5, 2015

It would be nice to be able to use some of the features of ES6, but AFAIK using Traceur/etc with this generator would involve changing a lot of code to be ES6 compatible

@jamiebuilds
Copy link

Hi, Babel contributor here. ES6 is actually pretty easy to get started with, it's completely backwards compatible so anything you previously wrote will continue to work, and you can start migrating features one by one and because Babel generates simple high-quality output you don't need to be locked into it forever like you would with Traceur.

If you need any help setting up or using Babel let me know or stop by our support chat: https://gitter.im/babel/babel

Awk34 pushed a commit that referenced this issue Jun 16, 2015
…g babel

Added a follow up question to the first language selection question to enable
ES6 client support with Babel.

Related issue: Any plans for es6 and traceur support? #684
Awk34 pushed a commit that referenced this issue Jun 17, 2015
…g babel

    Building on from the ES6 client preprocessor have added karma config and related
    karma-babel-preprocessor module for ES6 client tests for complete ES6 client support

    Related issue: Any plans for es6 and traceur support? #684
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants