Skip to content
This repository was archived by the owner on Nov 7, 2023. It is now read-only.

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 2, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
core-js 3.19.0 -> 3.33.2 age adoption passing confidence

Release Notes

zloirock/core-js (core-js)

v3.33.2

Compare Source

  • Simplified structuredClone polyfill, avoided second tree pass in cases of transferring
  • Added support of SuppressedError to structuredClone polyfill
  • Removed unspecified unnecessary ArrayBuffer and DataView dependencies of structuredClone lack of which could cause errors in some entries in IE10-
  • Fixed handling of fractional number part in Number.fromString
  • Compat data improvements:

v3.33.1

Compare Source

v3.33.0

Compare Source

v3.32.2

Compare Source

  • Fixed structuredClone feature detection core-js@3.32.1 bug, #​1288
  • Added a workaround of old WebKit + eval bug, #​1287
  • Compat data improvements:
    • Added Samsung Internet 23 compat data mapping
    • Added Quest Browser 29 compat data mapping

v3.32.1

Compare Source

  • Fixed some cases of IEEE754 rounding, #​1279, thanks @​petamoriken
  • Prevented injection process polyfill to core-js via some bundlers or esm.sh, #​1277
  • Some minor fixes and stylistic changes
  • Compat data improvements:

v3.32.0

Compare Source

v3.31.1

Compare Source

v3.31.0

Compare Source

v3.30.2

Compare Source

  • Added a fix for a NodeJS 20.0.0 bug with cloning File via structuredClone
  • Added protection from Terser unsafe String optimization, #​1242
  • Added a workaround for getting proper global object in Figma plugins, #​1231
  • Compat data improvements:

v3.30.1

Compare Source

v3.30.0

Compare Source

v3.29.1

Compare Source

v3.29.0

Compare Source

  • Added URLSearchParams.prototype.size getter, url/734
  • Allowed cloning resizable ArrayBuffers in the structuredClone polyfill
  • Fixed wrong export in /(stable|actual|full)/instance/unshift entries, #​1207
  • Compat data improvements:
    • Set methods proposal marked as supported from Bun 0.5.7
    • String.prototype.toWellFormed marked as fixed from Bun 0.5.7
    • Added Deno 1.31 compat data mapping

v3.28.0

Compare Source

3.28.0 - 2023.02.14

v3.27.2

Compare Source

  • Set methods proposal updates:
    • Closing of iterators of Set-like objects on early exit, proposal-set-methods/85
    • Some other minor internal changes
  • Added one more workaround of a webpack dev server bug on IE global methods, #​1161
  • Fixed possible String.{ raw, cooked } error with empty template array
  • Used non-standard V8 Error.captureStackTrace instead of stack parsing in new error classes / wrappers where it's possible
  • Added detection correctness of iteration to Promise.{ allSettled, any } feature detection, Hermes issue
  • Compat data improvements:
    • Change Array by copy proposal marked as supported from V8 ~ Chrome 110
    • Added Samsung Internet 20 compat data mapping
    • Added Quest Browser 25 compat data mapping
    • Added React Native 0.71 Hermes compat data
    • Added Electron 23 and 24 compat data mapping
    • self marked as fixed in Deno 1.29.3, deno/17362
  • Minor tweaks of minification settings for core-js-bundle
  • Refactoring, some minor fixes, improvements, optimizations

v3.27.1

Compare Source

  • Fixed a Chakra-based MS Edge (18-) bug that unfreeze (O_o) frozen arrays used as WeakMap keys
  • Fixing of the previous bug also fixes some cases of String.dedent in MS Edge
  • Fixed dependencies of some entries

v3.27.0

Compare Source

  • Iterator Helpers proposal:
    • Built-ins:
      • Iterator
        • Iterator.from
        • Iterator.prototype.drop
        • Iterator.prototype.every
        • Iterator.prototype.filter
        • Iterator.prototype.find
        • Iterator.prototype.flatMap
        • Iterator.prototype.forEach
        • Iterator.prototype.map
        • Iterator.prototype.reduce
        • Iterator.prototype.some
        • Iterator.prototype.take
        • Iterator.prototype.toArray
        • Iterator.prototype.toAsync
        • Iterator.prototype[@​@​toStringTag]
      • AsyncIterator
        • AsyncIterator.from
        • AsyncIterator.prototype.drop
        • AsyncIterator.prototype.every
        • AsyncIterator.prototype.filter
        • AsyncIterator.prototype.find
        • AsyncIterator.prototype.flatMap
        • AsyncIterator.prototype.forEach
        • AsyncIterator.prototype.map
        • AsyncIterator.prototype.reduce
        • AsyncIterator.prototype.some
        • AsyncIterator.prototype.take
        • AsyncIterator.prototype.toArray
        • AsyncIterator.prototype[@​@​toStringTag]
    • Moved to Stage 3, November 2022 TC39 meeting
    • Added /actual/ entries, unconditional forced replacement disabled for features that survived to Stage 3
    • .from accept strings, .flatMap throws on strings returned from the callback, proposal-iterator-helpers/244, proposal-iterator-helpers/250
    • .from and .flatMap throws on non-object iterators, proposal-iterator-helpers/253
  • Set methods proposal:
    • Built-ins:
      • Set.prototype.intersection
      • Set.prototype.union
      • Set.prototype.difference
      • Set.prototype.symmetricDifference
      • Set.prototype.isSubsetOf
      • Set.prototype.isSupersetOf
      • Set.prototype.isDisjointFrom
    • Moved to Stage 3, November 2022 TC39 meeting
    • Reimplemented with new semantics:
      • Optimized performance (iteration over lowest set)
      • Accepted only Set-like objects as an argument, not all iterables
      • Accepted only Sets as this, no @@​species support, and other minor changes
    • Added /actual/ entries, unconditional forced replacement changed to feature detection
    • For avoiding breaking changes:
      • New versions of methods are implemented as new modules and available in new entries or entries where old versions of methods were not available before (like /actual/ namespace)
      • In entries where they were available before (like /full/ namespace), those methods are available with fallbacks to old semantics (in addition to Set-like, they accept iterable objects). This behavior will be removed from the next major release
  • Well-Formed Unicode Strings proposal:
    • Methods:
      • String.prototype.isWellFormed
      • String.prototype.toWellFormed
    • Moved to Stage 3, November 2022 TC39 meeting
    • Added /actual/ entries, disabled unconditional forced replacement
  • Explicit resource management Stage 3 and Async explicit resource management Stage 2 proposals:
    • Renamed from "using statement" and split into 2 (sync and async) proposals
    • In addition to already present well-known symbols, added new built-ins:
      • Symbol.dispose
      • Symbol.asyncDispose
      • SuppressedError
      • DisposableStack
        • DisposableStack.prototype.dispose
        • DisposableStack.prototype.use
        • DisposableStack.prototype.adopt
        • DisposableStack.prototype.defer
        • DisposableStack.prototype.move
        • DisposableStack.prototype[@​@​dispose]
      • AsyncDisposableStack
        • AsyncDisposableStack.prototype.disposeAsync
        • AsyncDisposableStack.prototype.use
        • AsyncDisposableStack.prototype.adopt
        • AsyncDisposableStack.prototype.defer
        • AsyncDisposableStack.prototype.move
        • AsyncDisposableStack.prototype[@​@​asyncDispose]
      • Iterator.prototype[@​@​dispose]
      • AsyncIterator.prototype[@​@​asyncDispose]
    • Sync version of this proposal moved to Stage 3, November 2022 TC39 meeting
    • Added /actual/ namespace entries for Stage 3 proposal
  • Added String.dedent stage 2 proposal
    • Method String.dedent
    • Throws an error on non-frozen raw templates for avoiding possible breaking changes in the future, proposal-string-dedent/75
  • Compat data targets improvements:
    • React Native from 0.70 shipped with Hermes as the default engine. However, bundled Hermes versions differ from standalone Hermes releases. So added react-native target for React Native with bundled Hermes.
    • According to the documentation, Oculus Browser was renamed to Meta Quest Browser, so oculus target was renamed to quest.
    • opera_mobile target name is confusing since it contains data for the Chromium-based Android version, but iOS Opera is Safari-based. So opera_mobile target was renamed to opera-android.
    • android target name is also confusing for someone - that means Android WebView, some think thinks that it's Chrome for Android, but they have some differences. For avoiding confusion, added chrome-android target.
    • For consistency with two previous cases, added firefox-android target.
    • For avoiding breaking changes, the oculus and opera_mobile fields are available in the compat data till the next major release.
  • Compat data improvements:
  • { Map, WeakMap }.prototype.emplace became stricter by the spec draft
  • Smoothed behavior of some conflicting proposals
  • Removed some generic behavior (like @@​species pattern) of some .prototype methods from the new collections methods proposal and the Array deduplication proposal that most likely will not be implemented since it contradicts the current TC39 policy
  • Added pure version of the Number constructor, #​1154, #​1155, thanks @​trosos
  • Added set(Timeout|Interval|Immediate) extra arguments fix for Bun 0.3.0- (similarly to IE9-), bun/1633
  • Fixed handling of sparse arrays in structuredClone, #​1156
  • Fixed a theoretically possible future conflict of polyfills definitions in the pure version
  • Some refactoring and optimization

v3.26.1

Compare Source

  • Disabled forced replacing of Array.fromAsync since it's on Stage 3
  • Avoiding a check of the target in the internal function-uncurry-this helper where it's not required - minor optimization and preventing problems in some broken environments, a workaround of #​1141
  • V8 will not ship Array.prototype.{ group, groupToMap } in V8 ~ Chromium 108, proposal-array-grouping/44

v3.26.0

Compare Source

v3.25.5

Compare Source

  • Fixed regression with an error on reuse of some built-in methods from another realm, #​1133

v3.25.4

Compare Source

  • Added a workaround of a Nashorn bug with Function.prototype.{ call, apply, bind } on string methods, #​1128
  • Updated lists of [Serializable] and [Transferable] objects in the structuredClone polyfill. Mainly, for better error messages if polyfilling of cloning such types is impossible
  • Array.prototype.{ group, groupToMap } marked as supported from V8 ~ Chromium 108
  • Added Electron 22 compat data mapping

v3.25.3

Compare Source

  • Forced polyfilling of Array.prototype.groupToMap in the pure version for returning wrapped Map instances
  • Fixed existence of Array.prototype.{ findLast, findLastIndex } in /stage/4 entry
  • Added Opera Android 71 compat data mapping
  • Some stylistic changes

v3.25.2

Compare Source

  • Considering document.all as a callable in some missed cases
  • Added Safari 16.0 compat data
  • Added iOS Safari 16.0 compat data mapping
  • Fixed some ancient iOS Safari versions compat data mapping

v3.25.1

Compare Source

  • Added some fixes and workarounds of FF30- typed arrays bug that does not properly convert objects to numbers
  • Added sideEffects field to core-js-pure package.json for better tree shaking, #​1117
  • Dropped semver dependency from core-js-compat
    • semver package (ironically) added a breaking change and dropped NodeJS 8 support in the minor 7.1 version, after that semver in core-js-compat was pinned to 7.0 since for avoiding breaking changes it should support NodeJS 8. However, since core-js-compat is usually used with other packages that use semver dependency, it causes multiple duplication of semver in dependencies. So I decided to remove semver dependency and replace it with a couple of simple helpers.
  • Added Bun 0.1.6-0.1.11 compat data
  • Added Deno 1.25 compat data mapping
  • Updated Electron 21 compat data mapping
  • Some stylistic changes, minor fixes, and improvements

v3.25.0

Compare Source

  • Added Object.prototype.__proto__ polyfill
    • It's optional, legacy, and in some cases (mainly because of developers' mistakes) can cause problems, but some libraries depend on it, and most code can't work without the proper libraries' ecosystem
    • Only for modern engines where this feature is missed (like Deno), it's not installed in IE10- since here we have no proper way setting of the prototype
    • Without fixes of early implementations where it's not an accessor since those fixes are impossible
    • Only for the global version
  • Considering document.all as an object in some missed cases, see ECMAScript Annex B 3.6
  • Avoiding unnecessary promise creation and validation result in %WrapForValid(Async)IteratorPrototype%.return, proposal-iterator-helpers/215
  • Fixed omitting the result of proxing .return in %IteratorHelperPrototype%.return, #​1116
  • Fixed the order creation of properties of iteration result object of some iterators (value should be created before done)
  • Fixed some cases of Safari < 13 bug - silent on non-writable array .length setting
  • Fixed ArrayBuffer.length in V8 ~ Chrome 27-
  • Relaxed condition of re-usage native WeakMap for internal states with multiple core-js copies
  • Availability cloning of FileList in the structuredClone polyfill extended to some more old engines versions
  • Some stylistic changes and minor fixes
  • Throwing a TypeError in core-js-compat / core-js-builder in case of passing invalid module names / filters for avoiding unexpected result, related to #​1115
  • Added missed NodeJS 13.2 to esmodules core-js-compat / core-js-builder target
  • Added Electron 21 compat data mapping
  • Added Oculus Browser 23.0 compat data mapping

v3.24.1

Compare Source

  • NodeJS is ignored in IS_BROWSER detection to avoid a false positive with jsdom, #​1110
  • Fixed detection of @@&#8203;species support in Promise in some old engines
  • { Array, %TypedArray% }.prototype.{ findLast, findLastIndex } marked as shipped in FF104
  • Added iOS Safari 15.6 compat data mapping
  • Fixed Opera 15 compat data mapping

v3.24.0

Compare Source

v3.23.5

Compare Source

  • Fixed a typo in the structuredClone feature detection, #​1106
  • Added Opera Android 70 compat data mapping

v3.23.4

Compare Source

  • Added a workaround of the Bun ~ 0.1.1 bug that define some globals with incorrect property descriptors and that causes a crash of core-js
  • Added a fix of the FF103+ structuredClone bugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but .stack of the clone is an empty string
  • Fixed { Map, WeakMap }.prototype.emplace logic, #​1102
  • Fixed order of errors throwing on iterator helpers

v3.23.3

Compare Source

v3.23.2

Compare Source

  • Avoided creation of extra properties for the handling of %TypedArray% constructors in new methods, #​1092 (comment)
  • Added Deno 1.23 compat data mapping

v3.23.1

Compare Source

  • Fixed possible error on multiple core-js copies, #​1091
  • Added v flag to RegExp.prototype.flags implementation in case if current V8 bugs will not be fixed before this flag implementation

v3.23.0

Compare Source

  • Array find from last moved to the stable ES, according to June 2022 TC39 meeting:
    • Array.prototype.findLast
    • Array.prototype.findLastIndex
    • %TypedArray%.prototype.findLast
    • %TypedArray%.prototype.findLastIndex
  • Methods from the Array grouping proposal renamed, according to June 2022 TC39 meeting:
    • Array.prototype.groupBy -> Array.prototype.group
    • Array.prototype.groupByToMap -> Array.prototype.groupToMap
  • Changed the order of operations in %TypedArray%.prototype.with following proposal-change-array-by-copy/86, according to June 2022 TC39 meeting
  • Decorator Metadata proposal extracted from Decorators proposal as a separate stage 2 proposal, according to March 2022 TC39 meeting, Symbol.metadataKey replaces Symbol.metadata
  • Added Array.prototype.push polyfill with some fixes for modern engines
  • Added Array.prototype.unshift polyfill with some fixes for modern engines
  • Fixed a bug in the order of getting flags in RegExp.prototype.flags in the actual version of V8
  • Fixed property descriptors of some Math and Number constants
  • Added a workaround of V8 ArrayBufferDetaching protector cell invalidation and performance degradation on structuredClone feature detection, one more case of #​679
  • Added detection of NodeJS bug in structuredClone that can not clone DOMException (just in case for future versions that will fix other issues)
  • Compat data:
    • Added NodeJS 18.3 compat data mapping
    • Added and fixed Deno 1.22 and 1.21 compat data mapping
    • Added Opera Android 69 compat data mapping
    • Updated Electron 20.0 compat data mapping

v3.22.8

Compare Source

  • Fixed possible multiple call of ToBigInt / ToNumber conversion of the argument passed to %TypedArray%.prototype.fill in V8 ~ Chrome < 59, Safari < 14.1, FF < 55, Edge <=18
  • Fixed some cases of DeletePropertyOrThrow in IE9-
  • Fixed the kind of error (TypeError instead of Error) on incorrect exec result in RegExp.prototype.test polyfill
  • Fixed dependencies of { actual, full, features }/typed-array/at entries
  • Added Electron 20.0 compat data mapping
  • Added iOS Safari 15.5 compat data mapping
  • Refactoring

v3.22.7

Compare Source

  • Added a workaround for V8 ~ Chrome 53 bug with non-writable prototype of some methods, #​1083

v3.22.6

Compare Source

  • Fixed possible double call of ToNumber conversion on arguments of Math.{ fround, trunc } polyfills
  • Array.prototype.includes marked as fixed in FF102

v3.22.5

Compare Source

  • Ensured that polyfilled constructors .prototype is non-writable
  • Ensured that polyfilled methods .prototype is not defined
  • Added detection and fix of a V8 ~ Chrome <103 bug of struturedClone that returns null if cloned object contains multiple references to one error

v3.22.4

Compare Source

  • Ensured proper .length of polyfilled functions even in compressed code (excepting some ancient engines)
  • Ensured proper .name of polyfilled accessors (excepting some ancient engines)
  • Ensured proper source / ToString conversion of polyfilled accessors
  • Actualized Rhino compat data
  • Refactoring

v3.22.3

Compare Source

  • Added a fix for FF99+ Array.prototype.includes broken on sparse arrays

v3.22.2

Compare Source

  • Fixed URLSearchParams in IE8- that was broken in the previous release
  • Fixed __lookupGetter__ entries

v3.22.1

Compare Source

  • Improved some cases of RegExp flags handling
  • Prevented experimental warning in NodeJS ~ 18.0 on detection fetch API
  • Added NodeJS 18.0 compat data

v3.22.0

Compare Source

  • Change Array by copy proposal:
    • Moved to Stage 3, March TC39 meeting
    • Disabled forced replacement and added /actual/ entry points for methods from this proposal
    • Array.prototype.toSpliced throws a TypeError instead of RangeError if the result length is more than MAX_SAFE_INTEGER, proposal-change-array-by-copy/70
  • Added some more atob / btoa fixes:
    • NodeJS <17.9 atob does not ignore spaces, node/42530
    • Actual NodeJS atob does not validate encoding, node/42646
    • FF26- implementation does not properly convert argument to string
    • IE / Edge <16 implementation have wrong arity
  • Added /full/ namespace as the replacement for /features/ since it's more descriptive in context of the rest namespaces (/es//stable//actual//full/)
  • Avoided propagation of removed parts of proposals to upper stages. For example, %TypedArray%.prototype.groupBy was removed from the Array grouping proposal a long time ago. We can't completely remove this method since it's a breaking change. But this proposal has been promoted to stage 3 - so the proposal should be promoted without this method, this method should not be available in /actual/ entries - but it should be available in early-stage entries to avoid breakage.
  • Significant internal refactoring and splitting of modules (but without exposing to public API since it will be a breaking change - it will be exposed in the next major version)
  • Bug fixes:
    • Fixed work of non-standard V8 Error features with wrapped Error constructors, #​1061
    • null and undefined allowed as the second argument of structuredClone, #​1056
  • Tooling:
    • Stabilized proposals are filtered out from the core-js-compat -> core-js-builder -> core-js-bundle output. That mean that if the output contains, for example, es.object.has-own, the legacy reference to it, esnext.object.has-own, no longer added.
    • Aligned modules filters of core-js-builder and core-js-compat, now it's modules and exclude options
    • Added support of entry points, modules, regexes, and arrays of them to those filter

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 74d7b4f to fb161c5 Compare November 22, 2021 18:32
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from fb161c5 to 5c25d9f Compare November 29, 2021 21:38
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.19.1 fix(deps): update dependency core-js to v3.19.2 Nov 29, 2021
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 5c25d9f to b5e09ab Compare December 6, 2021 08:45
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.19.2 fix(deps): update dependency core-js to v3.19.3 Dec 6, 2021
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from b5e09ab to 9bc9da7 Compare December 15, 2021 20:22
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.19.3 fix(deps): update dependency core-js to v3.20.0 Dec 15, 2021
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 9bc9da7 to 44e9e6f Compare December 23, 2021 12:28
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.20.0 fix(deps): update dependency core-js to v3.20.1 Dec 23, 2021
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 44e9e6f to 8e21693 Compare January 1, 2022 19:48
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.20.1 fix(deps): update dependency core-js to v3.20.2 Jan 1, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 8e21693 to f02cb1d Compare January 15, 2022 11:48
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.20.2 fix(deps): update dependency core-js to v3.20.3 Jan 15, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from f02cb1d to 7f139bc Compare March 7, 2022 18:15
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.20.3 fix(deps): update dependency core-js to v3.21.1 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 7f139bc to e22f8bb Compare April 24, 2022 22:17
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.21.1 fix(deps): update dependency core-js to v3.22.2 Apr 24, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from e22f8bb to e076ac9 Compare May 15, 2022 20:27
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.22.2 fix(deps): update dependency core-js to v3.22.5 May 15, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from e076ac9 to cdaec2f Compare June 18, 2022 15:09
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.22.5 fix(deps): update dependency core-js to v3.23.1 Jun 18, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from cdaec2f to 7829e0d Compare June 23, 2022 22:55
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.23.1 fix(deps): update dependency core-js to v3.23.2 Jun 23, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 7829e0d to 93f71ec Compare September 25, 2022 13:00
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.23.2 fix(deps): update dependency core-js to v3.25.2 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 93f71ec to 885e9c9 Compare November 20, 2022 20:55
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.25.2 fix(deps): update dependency core-js to v3.26.1 Nov 20, 2022
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.26.1 fix(deps): update dependency core-js to v3.29.1 Mar 17, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 885e9c9 to 86ffc52 Compare March 17, 2023 08:10
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.29.1 fix(deps): update dependency core-js to v3.30.1 Apr 17, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 86ffc52 to 75a6131 Compare April 17, 2023 11:01
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.30.1 fix(deps): update dependency core-js to v3.30.2 May 28, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 75a6131 to d7e9ea7 Compare May 28, 2023 10:00
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from d7e9ea7 to eb5cdfe Compare June 11, 2023 22:37
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.30.2 fix(deps): update dependency core-js to v3.31.0 Jun 11, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from eb5cdfe to a8d147f Compare July 6, 2023 01:24
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.31.0 fix(deps): update dependency core-js to v3.31.1 Jul 6, 2023
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.31.1 fix(deps): update dependency core-js to v3.32.0 Jul 27, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from a8d147f to 642c34f Compare July 27, 2023 21:04
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.32.0 fix(deps): update dependency core-js to v3.32.1 Aug 18, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 642c34f to c6b3bb4 Compare August 18, 2023 18:37
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.32.1 fix(deps): update dependency core-js to v3.32.2 Sep 7, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from c6b3bb4 to e566636 Compare September 7, 2023 13:12
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from e566636 to 4a38241 Compare September 15, 2023 17:02
@renovate
Copy link
Contributor Author

renovate bot commented Sep 15, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @angular-devkit/build-angular@16.0.5
npm ERR! Found: @angular/compiler-cli@12.2.13
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"12.2.13" from the root project
npm ERR!   peer @angular/compiler-cli@"^12.0.0 || ^12.2.0-next.0" from ng-packagr@12.2.5
npm ERR!   node_modules/ng-packagr
npm ERR!     dev ng-packagr@"12.2.5" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler-cli@"^16.0.0" from @angular-devkit/build-angular@16.0.5
npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev @angular-devkit/build-angular@"16.0.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @angular/compiler-cli@16.2.11
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   peer @angular/compiler-cli@"^16.0.0" from @angular-devkit/build-angular@16.0.5
npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev @angular-devkit/build-angular@"16.0.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/79f05c/601d80/cache/others/npm/_logs/2023-10-30T19_15_07_936Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/79f05c/601d80/cache/others/npm/_logs/2023-10-30T19_15_07_936Z-debug-0.log

@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 4a38241 to 48b2b4f Compare October 1, 2023 18:46
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.32.2 fix(deps): update dependency core-js to v3.33.0 Oct 1, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 48b2b4f to 2e6bd2b Compare October 20, 2023 06:23
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.33.0 fix(deps): update dependency core-js to v3.33.1 Oct 20, 2023
@renovate renovate bot force-pushed the renovate/core-js-3.x branch from 2e6bd2b to 1b6db6e Compare October 30, 2023 19:15
@renovate renovate bot changed the title fix(deps): update dependency core-js to v3.33.1 fix(deps): update dependency core-js to v3.33.2 Oct 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant