Update core-js: 2.6.5 → 2.6.12 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ core-js (2.6.5 → 2.6.12) · Repo · Changelog

Release Notes

2.6.12

• Added code points / code units explicit feature detection in String#at for preventing breakage code which use obsolete String#at proposal polyfill
• Added OPEN_SOURCE_CONTRIBUTOR detection in postinstall
• Added Drone CI detection in postinstall

2.6.11

• Returned usage of node -e in the postinstall scripts for better cross-platform compatibility, #582
• Improved CI detection in the postinstall script, #707

2.6.10

• Show similar postinstall messages only once per npm i, #597

2.6.9

• Some fixes and improvements of the postinstall script like support npm color config (#556) or adding support of ADBLOCK env variable

2.6.8

• Added a workaround of a strange npx bug on postinstall, #551

2.6.7

• Added one more workaround of alternative not completely correct Symbol polyfills, #550, #554

2.6.6

• Fixed IE8- non-enumerable properties support in Object.{ assign, entries, values }, #541
• Fixed support of primitives in Object.getOwnPropertySymbols in Chrome 38 / 39, #539
• Show a message on postinstall

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 22 commits:

• 2.6.12
• make tests pass with the modern `String#matchAll`
• add code points / code units explicit feature detection in `String#at` for preventing breakage code which use obsolete `String#at` proposal polyfill
• update the `postinstall` script
• 2.6.11
• improve the `postinstall` script
• 2.6.10
• update the `postinstall` message
• backport the latest `postinstall` script related changes
• 2.6.9
• backport changes in the postinstall script
• 2.6.8
• add a workaround of a strange `npx` bug on `postinstall`, fix #551
• 2.6.7
• backport #549
• add an additional check of native `Symbol`
• fix links to `#raising-funds` section
• 2.6.6
• update readme
• show a message on postinstall
• backport fixes for #539
• backport fixes for #541

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)