SebastianVerified account

@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

@jasonmulligan It's not an opinion. It's spec behaviour.

@sebmck but the output isn't es6 code. why does it matter?

@jasonmulligan Because you're writing ES6, you aren't writing ES6-like code.

@sebmck you're right. god damn breaking changes between the versions of the language.