Skip to content

dependabot npm(deps): bump core-js from 3.27.2 to 3.28.0

Depen d'Abot requested to merge dependabot-npm_and_yarn-core-js-3.28.0 into master

Bumps core-js from 3.27.2 to 3.28.0.

Changelog

Sourced from core-js's changelog.

3.28.0 - 2023.02.14

I highly recommend reading this: So, what's next?

  • Change Array by copy proposal:
    • Methods:
      • Array.prototype.toReversed
      • Array.prototype.toSorted
      • Array.prototype.toSpliced
      • Array.prototype.with
      • %TypedArray%.prototype.toReversed
      • %TypedArray%.prototype.toSorted
      • %TypedArray%.prototype.with
    • Moved to stable ES, January 2023 TC39 meeting
    • Added es. namespace modules, /es/ and /stable/ namespaces entries
  • Added JSON.parse source text access Stage 3 proposal
    • Methods:
      • JSON.parse patched for support source in reviver function arguments
      • JSON.rawJSON
      • JSON.isRawJSON
      • JSON.stringify patched for support JSON.rawJSON
  • Added ArrayBuffer.prototype.transfer and friends Stage 3 proposal:
    • Built-ins:
      • ArrayBuffer.prototype.detached
      • ArrayBuffer.prototype.transfer (only in runtimes with native structuredClone with ArrayBuffer transfer support)
      • ArrayBuffer.prototype.transferToFixedLength (only in runtimes with native structuredClone with ArrayBuffer transfer support)
    • In backwards, in runtimes with native ArrayBuffer.prototype.transfer, but without proper structuredClone, added ArrayBuffer transfer support to structuredClone polyfill
  • Iterator Helpers proposal:
  • Explicit Resource Management Stage 3 and Async Explicit Resource Management Stage 2 proposals:
  • Added Symbol predicates Stage 2 proposal
    • Methods:
      • Symbol.isRegistered
      • Symbol.isWellKnown
  • Number.range Stage 1 proposal and method renamed to Iterator.range
  • Function.prototype.unThis Stage 0 proposal and method renamed to Function.prototype.demethodize
  • Fixed Safari String.prototype.toWellFormed ToString conversion bug
  • Improved some cases handling of array-replacer in JSON.stringify symbols handling fix
  • Fixed many other old JSON.{ parse, stringify } bugs (numbers instead of strings as keys in replacer, handling negative zeroes, spaces, some more handling symbols cases, etc.)
  • Fixed configurability and ToString conversion of some accessors
  • Added throwing proper errors on an incorrect context in some ArrayBuffer and DataView methods
  • Some minor DataView and %TypedArray% polyfills optimizations
  • Added proper error on the excess number of trailing = in the atob polyfill
  • Fixed theoretically possible ReDoS vulnerabilities in String.prototype.{ trim, trimEnd, trimRight }, parse(Int|Float), Number, atob, and URL polyfills in some ancient engines
  • Compat data improvements:
    • RegExp.prototype.flags marked as fixed from V8 ~ Chrome 111
    • Added Opera Android 73 compat data mapping
  • Added TypeScript definitions to core-js-builder
Commits
  • 6f721fa refresh
  • 93ad467 3.28.0
  • 91e0347 so, what's next?
  • 39c079b throw proper errors on an incorrect context in some ArrayBuffer and `DataVi...
  • 7e0399d some fixes
  • 139abbf add ArrayBuffer.prototype.transfer and friends Stage 3 proposal
  • 44cf9e8 fix theoretically possible ReDoS vulnerabilities
  • 2e44954 fix Safari 9 JSON.parse bug with handling negative zero + some whitespaces
  • be7ea2c improve handling of strings wrapped to rawJSON
  • e21fe93 add some tests
  • Additional commits viewable in compare view

Merge request reports

Loading