Babel/WebPack support

• Don't assume global this exists.

Better require usage, spec tracking

• Don't require encoding-indexes if they are already present
• Don't expect encoding-indexes to return object with indexes
• Update indexes to pick up windows-1255 change, add test
• Fix encode() behavior when called with falsy arguments
• Add 'first' qualifier to indexes error message

Bug Fixes

• gb18030 decoder: Use correct index (#49)
• Shift_JIS encoder: exclude certain jis0208 index entries
• Big5 encoder: exclude HKSCS extensions

Bye bye, UTF-16

Per a recent update to the Encoding Standard, encoding to UTF-16 is no longer supported by default.

Statistically speaking, there were no users of those encodings with the native implementations of the API in Chrome. There was also no other place where the Web required UTF-16 encoding - even pages served as UTF-16 post form data back as UTF-8, unlike other encodings.

Since this is breaking change for the polyfill, the minor release version was bumped. You can continue to use the NONSTANDARD_allowLegacyEncoding option and pass one of the UTF-16 labels (utf-16le, utf-16be, etc) to use these encodings.

Spec Alignment

Functional spec alignment changes:

• GB18030 2005 update
• gb18030 and U+E5E5
• ISO-2022-JP encoder errors

Other/refactoring:

• Fix ISO-2022-JP encoder
• Store error mode as string
• Closure type annotation: encode never returns null

Performance improvements

• Tweaks to the internal stream implementation to increase performance
• More internal documentation/refactoring to align with spec

Spec sync 2015-08-20

v0.5.3

Bump version

Bug fix

v0.5.1

Bump to 0.5.1

Spec Sync - 2014-12

v0.5.0

Bump to 0.5.0

Expose legacy encoding

Minor library update:

• Add NONSTANDARD_allowLegacyEncoding option to allow encoding to non-UTF encodings, for testing or when caller doesn't care about Web compatibility
• closure compiler compatibility