New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More →
core-js-builder
Advanced tools
core-js-builder - npm Package Versions
Changelog
- Added
String#matchAll, proposal - Added
Object#__(define|lookup)[GS]etter__, annex B ES2017 - Added
@@toPrimitivemethods toDateandSymbol - Fixed
%TypedArray%#slicein Edge ~ 13 (throws with@@speciesand wrapped / inherited constructor) - Some other minor fixes
Changelog
- Some minor
Promisefixes:- Browsers
rejectionhandledevent better HTML spec complaint - Errors in unhandled rejection handlers should not cause any problems
- Fixed typo in feature detection
- Browsers
Changelog
- Some
Promiseimprovements:- Feature detection:
- Added detection unhandled rejection tracking support - now it's available everywhere, #140
- Added detection
@@speciespattern support for completely correct subclassing - Removed usage
Object.setPrototypeOffrom feature detection and noisy console message about it in FF
Promise.allfixed for some very specific cases
- Feature detection:
Changelog
- API:
- ES5 polyfills are split and logic, used in other polyfills, moved to internal modules
- All entry point works in ES3 environment like IE8- without
core-js/(library/)es5 - Added all missed single entry points for ES5 polyfills
- Separated ES5 polyfills moved to the ES6 namespace. Why?
- Mainly, for prevent duplication features in different namespaces - logic of most required ES5 polyfills changed in ES6+:
- Already added changes for:
Objectstatics - should accept primitives, new whitespaces lists inString#trim,parse(Int|float),RegExp#toStringlogic,String#split, etc - Should be changed in the future:
@@speciesandToLengthlogic inArraymethods,Dateparsing,Function#bind, etc - Should not be changed only several features like
Array.isArrayandDate.now
- Already added changes for:
- Some ES5 polyfills required for modern engines
- Mainly, for prevent duplication features in different namespaces - logic of most required ES5 polyfills changed in ES6+:
- All old entry points should work fine, but in the next major release API can be changed
- All entry point works in ES3 environment like IE8- without
Object.getOwnPropertyDescriptorsmoved to the stage 3, January TC39 meeting- Added
umdoption for custom build process, #169 - Returned entry points for
Arraystatics, removed in2.0, for compatibility withbabel6and for future fixes
- ES5 polyfills are split and logic, used in other polyfills, moved to internal modules
- Deprecated:
Reflect.enumeratedeprecated and will be removed from the next major release, January TC39 meeting
- New Features:
- Added
Reflectmetadata API as a pre-strawman feature, #152:Reflect.defineMetadataReflect.deleteMetadataReflect.getMetadataReflect.getMetadataKeysReflect.getOwnMetadataReflect.getOwnMetadataKeysReflect.hasMetadataReflect.hasOwnMetadataReflect.metadata
- Implementation / fixes
Date#toJSON - Fixes for
parseIntandNumber.parseInt - Fixes for
parseFloatandNumber.parseFloat - Fixes for
RegExp#toString - Fixes for
Array#sort - Fixes for
Number#toFixed - Fixes for
Number#toPrecision - Additional fixes for
String#split(RegExp#@@split)
- Added
- Improvements:
- Correct subclassing wrapped collections,
NumberandRegExpconstructors with native class syntax - Correct support
SharedArrayBufferand buffers from other realms in typed arrays wrappers - Additional validations for
Object.{defineProperty, getOwnPropertyDescriptor}andReflect.defineProperty
- Correct subclassing wrapped collections,
- Bug Fixes:
- Fixed some cases
Array#lastIndexOfwith negative second argument
- Fixed some cases
Changelog
- Temporarily removed
lengthvalidation fromUint8Arrayconstructor wrapper. Reason - bug inwsmodule (->socket.io) which passes toBufferconstructor ->Uint8Arrayfloat and uses theV8bug for conversion to int (by the spec should be thrown an error). It creates problems for many people. I hope, it will be returned after fixing this bug inV8.