search

mozilla-rally / quantified-self-playtest

Mozilla Public License 2.0
0 stars 1 forks source link

Bump core-js from 3.10.1 to 3.18.0 #48

Closed dependabot[bot] closed 3 years ago

dependabot[bot] commented 3 years ago

Bumps core-js from 3.10.1 to 3.18.0.

Changelog

Sourced from core-js's changelog.

3.18.0 - 2021.09.20
  • Added Array.fromAsync stage 1 proposal:
    • Array.fromAsync
    • %TypedArray%.fromAsync
  • .name and .toString() on polyfilled functions improved in many different cases
  • Improved internal IsConstructor and IsCallable checks
  • Fixed some internal cases of GetMethod operation
  • Fixed a bug of MS Edge 18- parseInt / parseFloat with boxed symbols
  • Fixed es.array.{ index-of, last-index-of } compat data
  • Added Deno 1.15 compat data mapping
  • Some other minor fixes and optimizations
3.17.3 - 2021.09.09
  • Fixed some possible problems related to possible extension of %IteratorPrototype% and %AsyncIteratorPrototype% in the future
  • Fixed DOMTokenList.prototype.{ forEach, @@iterator, keys, values, entries } in old WebKit versions where element.classList is not an instance of global DOMTokenList
  • Added NodeJS 16.9 compat data mapping
  • Added Samsung Internet 16.0 compat data mapping
3.17.2 - 2021.09.03
  • Fixed missed cases of ES3 reserved words usage, related to #980
  • Fixed dependencies in one missed entry point
  • Some other minor fixes and optimizations
3.17.1 - 2021.09.02
  • Fixed missed modules-by-versions data
3.17.0 - 2021.09.02
3.16.4 - 2021.08.29
  • AsyncFromSyncIterator made stricter, related mainly to AsyncIterator.from and AsyncIterator.prototype.flatMap
  • Handling of optional .next arguments in (Async)Iterator methods is aligned with the current spec draft (mainly - ignoring the first passed to .next argument in built-in generators)
  • Behavior of .next, .return, .throw methods on AsyncIterator helpers proxy iterators aligned with the current spec draft (built-in async generators) (mainly - some early errors moved to returned promises)
  • Fixed some cases of safe iteration closing
  • Fixed dependencies of some entry points
3.16.3 - 2021.08.25
  • Fixed CreateAsyncFromSyncIterator semantic in AsyncIterator.from, related to #765
  • Added a workaround of a specific case of broken Object.prototype, #973
3.16.2 - 2021.08.17
  • Added a workaround of a Closure Compiler unsafe optimization, #972
  • One more fix crashing of Object.create(null) on WSH, #970
  • Added Deno 1.14 compat data mapping
3.16.1 - 2021.08.09

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 3 years ago

Superseded by #50.