-
Notifications
You must be signed in to change notification settings - Fork 621
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
Try to remove the need of angular-babel in Meteor 1.3 #1192
Comments
We could also recommend that people use TypeScript instead of
People would have to use the Do you think this is an option? |
@pbastowski that's a good idea. On the Typescript point, what package do you use today? please have a look at this discussion about adding an official |
@Urigo As far as typescript goes, I use my So, whose typescript package will be the one to rule them all :) ??? |
About Typescript - look in the issue - this one - https://github.com/barbatus/ts-compilers |
Hi @pbastowski, If we start using typescript in 1.3 as you suggest, and I will be glad if we could, are we going to miss the source mapping mechanism that we have right now? You now this is a big issue for me! And you helped me to solve this issue in the current version. I mean: are we going to "see" our typescript code in chrome debugger (or just the transpiled one)? Thanks and bye ... |
I think we can close this issue, since Meteor supports now |
Try to add all the features angular-babel has to the official ecmascript package so that we won't need to add it anymore in Meteor 1.3.
If not released in Meteor 1.3, update angular-babel to use the latest Babel as similar as possible to Meteor's.
Need to add "es7.decorators" and add babelHelpers like in here: https://github.com/Urigo/angular2-meteor/blob/feature/meteor1.3/tests/packages/babel-runtime/babel-runtime.js#L277-L337
Also related:
meteor/meteor#6028
meteor/meteor#6057
@pbastowski @kamilkisiela
The text was updated successfully, but these errors were encountered: