This is just for reference, but for some reason Meteor's new ES2015 modules package (in Meteor 1.3 Beta) won't import babel-runtime, so as a temporary workaround I disabled the runtime so that the symbols are defined inline.
Interesting. I'll keep an eye out -- switching to babel 6 is on my todo list. If the runtime transform is an issue with some systems (like meteor), I can leave it out. Thanks for the heads up.
I think using the runtime is the proper thing to do (in case the code gets bigger we avoid duplicate code), so I opened an issue on meteor/meteor about the import "not found" error that I'm getting.
This is just for reference, but for some reason Meteor's new ES2015
modules
package (in Meteor 1.3 Beta) won't importbabel-runtime
, so as a temporary workaround I disabled the runtime so that the symbols are defined inline.