SebastianVerified account

@jasonmulligan See http://6to5.org/docs/usage/polyfill … and https://github.com/zloirock/core-js …

@sebmck word, found that after the fact; gotta think about how i can utilize that in a package scenario where there's no outside deps

@jasonmulligan http://6to5.org/docs/usage/transformers/#self-contained … may be relevant. Automatically rewrites WeakMap/Map/Set/Promise etc to reference a runtime lib.

@sebmck hey, so, babel... 4.x.x has a serious bug; ( global ) => { ... }}( this ); ... this becomes undefined... breaking my tests

@jasonmulligan That's not a bug. It's been like that since 3.x. See https://github.com/babel/babel/issues/562 …

@sebmck the compile target is es5, so yeah it's a bug; in node it's global env, in browser it's window; it's a bug

@jasonmulligan In that issue if you want non-ES6 behaviour, although I'd strongly discourage it. You shouldn't be relying on that behaviour.

@sebmck that's an opinion, and the fact is it's legal in es5, and we're talking about targeting es5; it's rewriting for no reason