Repository navigation
Use ECMAScript 5 by default - #21
Conversation
|
👍 This would be a nice thing to merge. |
|
I just got bit by this again as well. Please merge or advise |
|
Will do -- but before I do ... what exactly is the change that this makes? Also, if you rebase it, I can merge cleanly. |
|
Stuff like var arr = [1, 2,];
var obj = {a: 1, b: 2,};will not compile without setting |
|
My issue is hard errors on terms that were reserved in EMCA 3 (the current default), but released in EMCA 5. Ember.js uses |
|
Mind rebasing so I can merge cleanly? |
|
Putting it together now On Tue, Dec 11, 2012 at 10:20 AM, Jeremy Ashkenas
|
|
Ok - it's ready. |
All modern browsers use ES5 as their standard, and it often causes confusion when Javascript files fail to compress, but work in the browser. I often run into this roadblock when using the Rails Asset Pipeline in development mode (no compression) vs precompiling (with compression).
This change makes ES5 the default compression.