[WIP] 2.0

[zloirock]

• Add implementations and fixes ArrayBuffer, DataView, all typed arrays constructors with all static and prototype methods. Really hard point. Typed Arrays #90
• Improve collections polyfills - O(1) and prevent possible leaking with frozen keys, correct observable state for object keys, WeakMap w/ frozen keys and garbage collection #134
• Add {keys, values, entries, @@iterator} methods to all DOM collections which should have iterable interface or should be inherited from Array
• Add basic support rejectionHandled event / onrejectionhandled handler to the Promise polyfill
• Rename String#{padLeft, padRight} -> String#{padStart, padEnd}, proposal, November TC39 meeting (they want to rename it on each meeting?O_o), Update padLeft/padRight to be padStart/padEnd, #132
• Add String#{trimStart, trimEnd} as aliases for String#{trimLeft, trimRight}, proposal, November TC39 meeting
• Add System.global, proposal, November TC39 meeting
• Add Error.isError, proposal, November TC39 meeting
• Remove usage @@species from Promise.{all, race}, November TC39 meeting
• Check changes by meeting notes
• Add Math.{iaddh, isubh, imulh, umulh}, proposal
• Move RegExp.escape from es7 to non-standard core namespace, July TC39 meeting - too slow, but it's condition of stability, Remove RegExp.escape #116
• Add annex B HTML methods - ugly, but also the part of the spec
• Add little fix for Date#toString - new Date(NaN).toString() should be 'Invalid Date'
• Remove core.log module
• Remove Mozilla Array generics - deprecated and will be removed from FF, looks like strawman is dead. Available alternative shim.
• Change $ prefix for internal modules file names because (holy shit!) Team Foundation Server does not support it, "$" symbol in file names #129 (please, don't use core-js internal modules in your scripts!)
• Move custom build from external scripts to the separate package for preventing problems with dependencies, some changes in that API
• Add entry points for virtual methods
• Add entry points for stages proposals

...and if the situation does not change, it can be the last big release :(

[zloirock]

@Arnavion can you confirm the list of required DOM collections? Current list based on this your issue and comments. I'm not an expert in W3C and WHATWG specs and currently have no time to explore it.

[zloirock]

@guybedford will not System.global have a conflict with SystemJS?

[zloirock]

Any more ideas about this release?

[guybedford]

@zloirock thanks for the ping. System.global is actually already defined by SystemJS. Am I right in thinking that https://github.com/zloirock/core-js/blob/master/modules/_export.js#L21 is non-destructive so this should work out ok?

We do need to move to System.loader instead of treating System as the loader though anyway as soon as the WhatWG spec is stable enough to switch.

[zloirock]

@guybedford previously available System object will not be overridden. Main here - the second your point requires additional feature detection.

[Arnavion]

Sorry, I haven't been keeping up with this space. @saschanaz or users of core-js may have something to say.

BTW note the list in my comment you linked was built from experimenting with Nightly and is not based off spec(s). For example MimeTypeArray doesn't seem to be iterable. It's a mess...

Maybe just expect everyone to use Array.from ...

[saschanaz]

I had some time to quickly explore spec documents.

Yes:

1. MediaList, StyleSheetList, and CSSRuleList are iterable as they are ArrayClasses according to the latest CSSOM working draft and the latest editor's draft.
2. NodeList and DOMTokenList are iterable according to the W3C DOM4 final spec.

No:

1. DOMStringList is not iterable and is deprecated according to W3C DOM4 final spec.
2. HTMLCollection is not iterable according to the DOM4 spec.
3. NamedNodeMap is not iterable according to the W3C and WHATWG DOM4 docs.
4. FileList is not iterable according to File API working draft.
5. MimeTypeArray, PluginArray, and Plugin are not iterable according to HTML5 and HTML5.1 draft specs.
6. TouchList is not iterable according to Touch Events Level 2 spec.

[zloirock]

@Arnavion @saschanaz thanks for replies.

HTMLCollection is not iterable according to the DOM4 spec.

Interesting because iterable HTMLCollection - very frequent issue (#37, #68, in other trackers and chats...). If most DOM collections not required - maybe makes no sense replace Symbol in Chromium 38-40, just patch some methods, need to test it.

Some days I will not change this list, maybe someone else clarify it.

[zloirock]

Done.