chore(deps): update all non-major dependencies#12
chore(deps): update all non-major dependencies#12renovate[bot] wants to merge 1 commit intodevelopfrom
Conversation
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
132ca96 to
752c0ce
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
d7ec995 to
6b18cc0
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
d7bddd7 to
cc60f8f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
cc60f8f to
8247329
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
3abb9e0 to
c410c23
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
c410c23 to
e627c35
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
ca2851b to
0de9005
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
bbb5fc0 to
14b3411
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
99d07f5 to
623ad7c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
623ad7c to
8418717
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8418717 to
b58762d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
9eb2384 to
39f0c6c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
94b5342 to
220d767
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
758773d to
982070e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
ef5e7b9 to
e963bea
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
e963bea to
92f86a5
Compare
⚠ Artifact update problemRenovate 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:
The artifact failure details are included below: File name: drupal/composer.lock |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
00bb3f0 to
3959abd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
8727037 to
f56e83a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
f56e83a to
26be9c5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
060b542 to
55401dd
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
55401dd to
a395353
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
15da7f3 to
f3eabdb
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
f3eabdb to
8d351ba
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8d351ba to
58c7353
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
58c7353 to
930a55a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
ef570e2 to
95f2273
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
drupal/composer.json (1)
20-20: Updatecomposer.lockto matchcomposer.jsonfordrupal/core-composer-scaffold.The
composer.jsonspecifiesdrupal/core-composer-scaffoldversion9.5.11, but thecomposer.lockstill references version9.4.5. Ensure that thecomposer.lockfile is updated to reflect the correct version.
drupal/composer.lock: Update thedrupal/core-composer-scaffoldversion to9.5.11.Analysis chain
Verify compatibility with
drupal/core-composer-scaffold9.5.11.Ensure that the updated version of
drupal/core-composer-scaffolddoes not introduce breaking changes and is compatible with the existing codebase.
Verify the presence and version of
drupal/core-composer-scaffoldincomposer.jsonandcomposer.lock.Check if there are any references to
drupal/core-composer-scaffoldin documentation or scripts to ensure compatibility with the updated version.
Locate
composer.jsonandcomposer.lockfiles and verify the presence and version ofdrupal/core-composer-scaffold.Use
fdto find thecomposer.jsonandcomposer.lockfiles and then search for thedrupal/core-composer-scaffoldpackage within them.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility of `drupal/core-composer-scaffold` 9.5.11 with the existing codebase. # Test: Search for `drupal/core-composer-scaffold` usage. Expect: No breaking changes. rg --type php -A 5 'core-composer-scaffold'Length of output: 43
Script:
#!/bin/bash # Check for `drupal/core-composer-scaffold` in composer.json and composer.lock rg 'drupal/core-composer-scaffold' composer.json composer.lock # Search for references to `drupal/core-composer-scaffold` in documentation and scripts rg 'core-composer-scaffold' --type md --type shLength of output: 218
Script:
#!/bin/bash # Locate composer.json and composer.lock files fd composer.json fd composer.lock # Once located, search for `drupal/core-composer-scaffold` in these files fd composer.json --exec rg 'drupal/core-composer-scaffold' {} fd composer.lock --exec rg 'drupal/core-composer-scaffold' {}Length of output: 718
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
nuxt/package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (2)
- drupal/composer.json (1 hunks)
- nuxt/package.json (1 hunks)
Additional comments not posted (12)
nuxt/package.json (5)
13-13: Verify compatibility withdruxt-site^0.14.3.Ensure that the updated version of
druxt-sitedoes not introduce breaking changes and is compatible with the existing codebase.
17-17: Verify compatibility with@nuxt/image^0.7.2.Ensure that the updated version of
@nuxt/imagedoes not introduce breaking changes and is compatible with the existing codebase.Verification successful
Verify compatibility with
@nuxt/image^0.7.2.The changelog for
@nuxt/image^0.7.2 does not indicate any breaking changes. The update includes minor enhancements and bug fixes. The usage innuxt/nuxt.config.jsshould remain compatible.
nuxt/nuxt.config.jsScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility of `@nuxt/image` ^0.7.2 with the existing codebase. # Test: Search for `@nuxt/image` usage. Expect: No breaking changes. rg --type js --type ts -A 5 '@nuxt/image'Length of output: 296
Script:
#!/bin/bash # Fetch the changelog or release notes for `@nuxt/image` ^0.7.2 to verify compatibility. # Fetch the changelog URL from the package repository PACKAGE_NAME="@nuxt/image" PACKAGE_VERSION="0.7.2" PACKAGE_URL=$(npm view $PACKAGE_NAME@$PACKAGE_VERSION repository.url) # Extract the changelog content curl -s "${PACKAGE_URL%.*}/blob/master/CHANGELOG.md"Length of output: 217
Script:
#!/bin/bash # Directly fetch the changelog for `@nuxt/image` from the GitHub repository to verify compatibility. # Define the GitHub repository URL for `@nuxt/image` REPO_URL="https://raw.githubusercontent.com/nuxt/image/main/CHANGELOG.md" # Fetch the changelog content curl -s $REPO_URLLength of output: 57694
14-14: Verify compatibility withnuxt2.18.1.Ensure that the updated version of
nuxtdoes not introduce breaking changes and is compatible with the existing codebase.
20-20: Verify compatibility withpostcss8.4.41.Ensure that the updated version of
postcssdoes not introduce breaking changes and is compatible with the existing codebase.
12-12: Verify compatibility withcore-js3.38.0.Ensure that the updated version of
core-jsdoes not introduce breaking changes and is compatible with the existing codebase.drupal/composer.json (7)
21-21: Verify compatibility withdrupal/core-project-message9.5.11.Ensure that the updated version of
drupal/core-project-messagedoes not introduce breaking changes and is compatible with the existing codebase.Verification successful
The update to
drupal/core-project-message9.5.11 does not introduce breaking changes.The references to
core-project-messageare confined tocomposer.jsonandcomposer.lockfiles, indicating that it is used for project setup messages rather than runtime behavior. The update is safe and compatible with the existing codebase.
drupal/composer.jsondrupal/composer.lockScripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility of `drupal/core-project-message` 9.5.11 with the existing codebase. # Test: Search for `drupal/core-project-message` usage. Expect: No breaking changes. rg --type php -A 5 'core-project-message'Length of output: 41
Script:
#!/bin/bash # Description: Verify compatibility of `drupal/core-project-message` 9.5.11 with the existing codebase by searching for its references in various file types. # Test: Search for `core-project-message` usage in PHP, YAML, and JSON files. Expect: No breaking changes. rg 'core-project-message' -tphp -tyaml -tjson -A 5Length of output: 2803
22-22: Verify compatibility withdrupal/core-recommended9.5.11.Ensure that the updated version of
drupal/core-recommendeddoes not introduce breaking changes and is compatible with the existing codebase.
24-24: Verify compatibility withdrupal/tome^1.12.0.Ensure that the updated version of
drupal/tomedoes not introduce breaking changes and is compatible with the existing codebase.
23-23: Verify compatibility withdrupal/druxt1.2.0.Ensure that the updated version of
drupal/druxtdoes not introduce breaking changes and is compatible with the existing codebase.
18-18: Verify compatibility withcomposer/installers2.3.0.Ensure that the updated version of
composer/installersdoes not introduce breaking changes and is compatible with the existing codebase.
28-28: Verify compatibility withdrupal/core-dev9.5.11.Ensure that the updated version of
drupal/core-devdoes not introduce breaking changes and is compatible with the existing codebase.
25-25: Verify compatibility withdrush/drush^11.6.0.Ensure that the updated version of
drush/drushdoes not introduce breaking changes and is compatible with the existing codebase.Verification successful
Verify compatibility with
drush/drush^11.6.0.The update to
drush/drush^11.6.0 does not introduce breaking changes for the standard Drush commands used in thetome_drushnamespace. The commandssite-install,pm:enable,tome:import,cache:rebuild, andtome:exportshould function correctly with the new version.
drupal/drush/Commands/contrib/tome_drush/InstallCommands.php: Verified usage of standard Drush commands.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify compatibility of `drush/drush` ^11.6.0 with the existing codebase. # Test: Search for `drush/drush` usage. Expect: No breaking changes. rg --type php -A 5 'drush/drush'Length of output: 32
Script:
#!/bin/bash # Description: Verify compatibility of `drush/drush` ^11.6.0 with the existing codebase. # Test 1: Search for `drush/drush` usage in PHP files. rg --type php 'drush/drush' # Test 2: Search for `drush/drush` usage in YAML files (common for Drupal configurations). rg --type yaml 'drush/drush' # Test 3: Search for `drush/drush` usage in JSON files. rg --type json 'drush/drush' # Test 4: Search for `drush/drush` usage in Markdown files (documentation). rg --type md 'drush/drush'Length of output: 469
Script:
#!/bin/bash # Description: Verify compatibility of `drush/drush` ^11.6.0 with the existing codebase. # Test 1: Search for `tome_drush` commands in PHP files. rg --type php 'tome_drush' # Test 2: Search for `tome_drush` configurations in YAML files. rg --type yaml 'tome_drush' # Test 3: Search for `tome_drush` references in JSON files. rg --type json 'tome_drush' # Test 4: Search for `tome_drush` references in Markdown files (documentation). rg --type md 'tome_drush'Length of output: 1000
Script:
#!/bin/bash # Description: Verify compatibility of `drush/drush` ^11.6.0 with the existing codebase. # Test 1: Search for command definitions in `InstallCommands.php`. rg --type php 'function ' drupal/drush/Commands/contrib/tome_drush/InstallCommands.php # Test 2: Search for usage of `tome_drush` commands in PHP files. rg --type php 'tome_drush' # Test 3: Search for `drush` command definitions in the `tome_drush` namespace. rg --type php 'drush' drupal/drush/Commands/contrib/tome_drush/Length of output: 1853
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
nuxt/package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (2)
- drupal/composer.json (1 hunks)
- nuxt/package.json (1 hunks)
Additional comments not posted (11)
nuxt/package.json (5)
17-17: Update to@nuxt/imageversion ^0.7.2.The
@nuxt/imagepackage has been updated from ^0.7.1 to ^0.7.2. This minor update might include optimizations or small features.
14-14: Update tonuxtversion 2.18.1.The
nuxtframework has been updated from 2.15.8 to 2.18.1. Check for any deprecated features or enhancements that might affect your application.
20-20: Update topostcssversion 8.4.41.The
postcsspackage has been updated from 8.4.16 to 8.4.41. Ensure that any plugins or configurations used with PostCSS are compatible with this version.
12-12: Update tocore-jsversion 3.38.1.This update moves
core-jsfrom version 3.25.1 to 3.38.1. Ensure compatibility with any polyfills or features used in your project.
13-13: Update todruxt-siteversion ^0.14.3.The
druxt-sitepackage has been updated from ^0.13.0 to ^0.14.3. Verify that any new features or changes are compatible with your current setup.drupal/composer.json (6)
18-18: Update tocomposer/installersversion 2.3.0.The
composer/installerspackage has been updated from 2.2.0 to 2.3.0. Ensure that any custom installation paths or configurations are still valid.
20-22: Update to Drupal core components.The following Drupal core components have been updated:
drupal/core-composer-scaffoldfrom 9.4.5 to 9.5.11drupal/core-project-messagefrom 9.4.5 to 9.5.11drupal/core-recommendedfrom 9.4.5 to 9.5.11These updates might include important security fixes and improvements. Ensure compatibility with your existing Drupal setup.
28-28: Update todrupal/core-devversion 9.5.11.The
drupal/core-devpackage has been updated from 9.4.5 to 9.5.11. This update might include development tools or testing improvements.
25-25: Update todrush/drushversion ^11.6.0.The
drush/drushpackage has been updated from ^11.1 to ^11.6.0. Verify that any Drush commands or scripts are compatible with this version.
23-23: Update todrupal/druxtversion 1.2.0.The
drupal/druxtpackage has been updated from 1.1.1 to 1.2.0. Review any changes in the API or behavior that might affect your project.
24-24: Update todrupal/tomeversion ^1.12.0.The
drupal/tomepackage has been updated from ^1.7 to ^1.12.0. Ensure compatibility with your current setup and any new features introduced.
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
nuxt/package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (2)
- drupal/composer.json (1 hunks)
- nuxt/package.json (1 hunks)
Additional comments not posted (13)
nuxt/package.json (5)
12-12: LGTM! But verify the application functionality.The
core-jsdependency has been updated to a newer minor version, which may introduce new features or polyfills. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
13-13: LGTM! But verify the application functionality.The
druxt-sitedependency has been updated to a newer minor version, which may include enhancements or bug fixes relevant to the Druxt framework. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
14-14: LGTM! But verify the application functionality.The
nuxtdependency has been updated to a newer minor version, which likely brings improvements and new features to the Nuxt.js framework. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
17-17: LGTM! But verify the application functionality.The
@nuxt/imagedependency has been updated to a newer patch version, which may include minor updates or fixes. The change is unlikely to cause any issues, but it's still good to verify that the application still works as expected.
20-20: LGTM! But verify the application functionality.The
postcssdependency has been updated to a newer patch version, which could affect the CSS processing capabilities of the project. The change is unlikely to cause any issues, but it's still good to verify that the application still works as expected.drupal/composer.json (8)
18-18: LGTM! But verify the application functionality.The
composer/installersdependency has been updated to a newer minor version, which may include new features or improvements. The change is unlikely to cause any issues, but it's still good to verify that the application still works as expected.
20-20: LGTM! But verify the application functionality.The
drupal/core-composer-scaffolddependency has been updated to a newer minor version, which may include new features, improvements, and security patches. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
21-21: LGTM! But verify the application functionality.The
drupal/core-project-messagedependency has been updated to a newer minor version, which may include new features, improvements, and security patches. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
22-22: LGTM! But verify the application functionality.The
drupal/core-recommendeddependency has been updated to a newer minor version, which may include new features, improvements, and security patches. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
23-23: LGTM! But verify the application functionality.The
drupal/druxtdependency has been updated to a newer minor version, which may include new features, improvements, and bug fixes. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
24-24: LGTM! But verify the application functionality.The
drupal/tomedependency has been updated to a newer minor version, which may include new features, improvements, and bug fixes. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
25-25: LGTM! But verify the application functionality.The
drush/drushdependency has been updated to a newer minor version, which may include new features, improvements, and bug fixes. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
28-28: LGTM! But verify the application functionality.The
drupal/core-devdependency has been updated to a newer minor version, which may include new features, improvements, and security patches. The change is unlikely to cause any breaking changes, but it's important to verify that the application still works as expected.
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files ignored due to path filters (1)
nuxt/package-lock.jsonis excluded by!**/package-lock.json
Files selected for processing (2)
- drupal/composer.json (1 hunks)
- nuxt/package.json (1 hunks)
Files skipped from review as they are similar to previous changes (2)
- drupal/composer.json
- nuxt/package.json
|
This PR contains the following updates:
^0.7.1→^0.7.22.2.0→2.3.03.25.1→3.48.09.4.5→9.5.119.4.5→9.5.119.4.5→9.5.119.4.5→9.5.111.1.1→1.2.1^1.7→^1.14.0^11.1→^11.6.0^0.13.0→^0.14.32.15.8→2.18.18.4.16→8.5.8Release Notes
nuxt/image (@nuxt/image)
v0.7.2Compare Source
composer/installers (composer/installers)
v2.3.0Compare Source
Added
zloirock/core-js (core-js)
v3.48.0Compare Source
Mapupsert proposal:Map.prototype.getOrInsertMap.prototype.getOrInsertComputedWeakMap.prototype.getOrInsertWeakMap.prototype.getOrInsertComputedes.namespace modules,/es/and/stable/namespaces entriesCreateDataProperty/CreateDataPropertyOrThrowin some missed cases, #1497RegExpconstructor (NCG anddotAll) polyfill.lengthIterator.prototype.flatMapthrows on iterator withoutreturnmethodUint8Array.prototype.setFromHexthrows an error on length-tracking views over ResizableArrayBufferMapupsert proposal features marked as shipped in V8 ~ Chrome 145Iterator.concatmarked as shipped in Bun 1.3.7Iterator.prototype.flatMapmarked as supported from Safari 26.2 and Bun 1.2.21 because of a bug: throws on iterator withoutreturnmethodUint8Array.prototype.setFromHexmarked as supported from V8 ~ Chromium 144 because of a bug: throws an error on length-tracking views over ResizableArrayBufferv3.47.0Compare Source
JSON.parsesource text access proposal :JSON.isRawJSONJSON.parseJSON.rawJSONJSON.stringifyes.namespace modules,/es/and/stable/namespaces entriesJSON.stringifyinternalsIteratorsequencing proposal:Iterator.concates.namespace modules,/es/and/stable/namespaces entriesIterator.zipIterator.zipKeyed/actual/namespace entries, unconditional forced replacement changed to feature detection.sizeinURLSearchParams.prototype.appendpolyfill in IE8-Iterator.concatmarked as shipped in FF147Mapupsert proposal features marked as shipped in Safari 26.2Math.sumPrecisemarked as shipped in Safari 26.2Uint8Array.{ fromBase64, prototype.setFromBase64 }marked as fixed in Safari 26.2v3.46.0Compare Source
Mapupsert stage 3 proposal:WeakMap.prototype.getOrInsertComputedbug with callback calling before validation a keyIteratorchunking proposal:Iterator.prototype.chunksIterator.prototype.windowsIterator.prototype.slidingmethod replaced with an extra parameter ofIterator.prototype.windowsmethod, tc39/proposal-iterator-chunking/#24, tc39/proposal-iterator-chunking/#26Iterator.zipandIterator.zipKeyedbehavior withmode: 'longest'option, #1469, thanks @lionel-roweObject.groupByandIterator.zipKeyedtogether withSymbolpolyfill - some cases of symbol keys on resultnull-prototype object were able to leak out tofor-inMapupsert proposal features marked as shipped from FF144v3.45.1Compare Source
Mapupsert proposal with polyfilled methods in the pure versionbugsfields topackage.jsonof all packagesMapupsert proposal features marked as shipped from Bun 1.2.20v3.45.0Compare Source
Uint8Arrayto / from base64 and hex proposal:Uint8Array.fromBase64Uint8Array.fromHexUint8Array.prototype.setFromBase64Uint8Array.prototype.setFromHexUint8Array.prototype.toBase64Uint8Array.prototype.toHexes.namespace modules,/es/and/stable/namespaces entriesUint8ArrayfromBase64 / setFromBase64 does not throw an error on incorrect length of base64 stringMath.sumPreciseproposal:Math.sumPrecisees.namespace module,/es/and/stable/namespaces entriesIteratorsequencing proposal:Iterator.concat/actual/namespace entries, unconditional forced replacement changed to feature detectionMapupsert proposal:Map.prototype.getOrInsertMap.prototype.getOrInsertComputedWeakMap.prototype.getOrInsertWeakMap.prototype.getOrInsertComputed/actual/namespace entries, unconditional forced replacement changed to feature detectionIteratormethods/stage/entriesUint8Arrayto / from base64 and hex proposal features marked as supported from V8 ~ Chromium 140Uint8Array.{ fromBase64, prototype.setFromBase64 }marked as unsupported in Safari and supported only from Bun 1.2.20 because of a bug: it does not throw an error on incorrect length of base64 string%TypedArray%.prototype.withmarked as fixed in Safari 26.0v3.44.0Compare Source
Uint8Arrayto / from base64 and hex stage 3 proposal:Uint8Array.fromHexandUint8Array.prototype.{ setFromBase64, toBase64, toHex }, thanks @brc-ddGetinIterator.zipKeyed, following tc39/proposal-joint-iteration#43Iteratorsequencing stage 2.7 proposal:Iterator.concatno longer reusesIteratorResultobject of concatenated iterators, following tc39/proposal-iterator-sequencing#26Iteratorchunking stage 2 proposal:Iterator.prototype.slidingNumber.prototype.clampstage 2 proposal:clampno longer throws an error onNaNasminormax, following tc39/proposal-math-clamp#d2387791c265edf66fbe2455eab919016717ce6fSet.prototype.{ symmetricDifference, union }detectionIteratormethods/full/{ instance, number/virtual }/clampentriesIteratorhelpers marked as fixed and updated following the latest spec changes in Safari 26.0Set.prototype.{ difference, symmetricDifference, union }marked as fixed in Safari 26.0SuppressedErrormarked as fixed in FF141Error.isErrormarked as fixed in Node 24.3setImmediateandclearImmediatemarked as available from Deno 2.4Math.sumPrecisemarked as shipped in Bun 1.2.18%TypedArray%.prototype.withmarked as fixed in Bun 1.2.18v3.43.0Compare Source
Symbol.disposeSymbol.asyncDisposeSuppressedErrorDisposableStackDisposableStack.prototype.disposeDisposableStack.prototype.useDisposableStack.prototype.adoptDisposableStack.prototype.deferDisposableStack.prototype.moveDisposableStack.prototype[@​@​dispose]AsyncDisposableStackAsyncDisposableStack.prototype.disposeAsyncAsyncDisposableStack.prototype.useAsyncDisposableStack.prototype.adoptAsyncDisposableStack.prototype.deferAsyncDisposableStack.prototype.moveAsyncDisposableStack.prototype[@​@​asyncDispose]Iterator.prototype[@​@​dispose]AsyncIterator.prototype[@​@​asyncDispose]es.namespace module,/es/and/stable/namespaces entriesArray.fromAsyncproposal:Array.fromAsynces.namespace module,/es/and/stable/namespaces entriesError.isErrorproposal:Error.isErrores.namespace module,/es/and/stable/namespaces entriesIterator.zipIterator.zipKeyedIteratorchunking stage 2 proposal:Iterator.prototype.chunksIterator.prototype.windowsNumber.prototype.clampproposal:Number.prototype.clampMath.clampwas replaced withNumber.prototype.clampRangeErrorifmin <= maxor+0min and-0max, tc39/proposal-math-clamp/#22flagsgetter PR. Native methods are not fixed, only own implementation updated for:RegExp.prototype[@​@​match]RegExp.prototype[@​@​replace]RegExpflags in polyfills of some methods in engines without proper support ofRegExp.prototype.flagsand without polyfill of this getterthisis updated whileSet.prototype.differenceis being executedthisin the following methods:Set.prototype.symmetricDifferenceSet.prototype.unionIterator.prototype.dropIterator.prototype.filterIterator.prototype.flatMapIterator.prototype.mapIterator.fromwhen underlying iterator'sreturnmethod isnullArray.prototype.withwhen index coercion failsTypedArray.prototype.withshould truncate negative fractional index to zero, but instead throws an errorPromisepolyfill in the pure version/iterator/flat-mapentriesError.isErrormarked not supported in Node because of a bugSet.prototype.differencemarked as not supported in Safari and supported only from Bun 1.2.5 because of a bugSet.prototype.{ symmetricDifference, union }marked as not supported in Safari and supported only from Bun 1.2.5 because of a bugIterator.frommarked as not supported in Safari and supported only from Bun 1.2.5 because of a bugIteratorhelpers marked as implemented from FF141Array.prototype.withmarked as supported only from FF140 because it throws an incorrect exception when index coercion failsTypedArray.prototype.withmarked as unsupported in Bun and Safari because it should truncate negative fractional index to zero, but instead throws an errorDisposableStackandAsyncDisposableStackmarked as shipped in FF141 (SuppressedErrorhas a bug)AsyncDisposableStackbugs marked as fixed in Deno 2.3.2SuppressedErrorbugs (extra arguments support and arity) marked as fixed in Bun 1.2.15v3.42.0Compare Source
Mapupsert proposal:WeakMap.prototype.getOrInsertComputedupdated following tc39/proposal-upsert#79Map.prototype.getOrInsertMap.prototype.getOrInsertComputedWeakMap.prototype.getOrInsertWeakMap.prototype.getOrInsertComputedSymbolmethods forRegExpon primitive values following tc39/ecma262#3009:core-jsimplementationsString.prototype.matchAllString.prototype.matchString.prototype.replaceAllString.prototype.replaceString.prototype.searchString.prototype.splitUint8Array.prototype.setFromBase64bug in some of Linux builds of WebKitIterator.prototype.dropIterator.prototype.everyIterator.prototype.filterIterator.prototype.findIterator.prototype.flatMapIterator.prototype.forEachIterator.prototype.mapIterator.prototype.reduceIterator.prototype.someIterator.prototype.takeAsyncIteratorhelpersArray.fromAsync(due to the lack of async feature detection capability - temporarily, only in owncore-jsimplementation)AsyncIterator.fromIterator.prototype.toAsyncundefinedinitial parameter inIterator.prototype.reduce(see WebKit bug)core-js-compatandcore-js-builderAPI:'intersect'support fortargets.esmodules(Babel 7 behavior)targets.esmodules: true(Babel 7 behavior)RegExp.escapemarked as shipped from V8 ~ Chromium 136Error.isErrormarked as shipped from FF138Iteratorhelpers proposal features marked as supported from Deno 1.38.1 since it seems they were disabled in 1.38.0Iterator.prototype.{ drop, reduce, take }methods marked as fixed in Bun 1.2.11v3.41.0Compare Source
RegExp.escapeproposal:RegExp.escapees.namespace module,/es/and/stable/namespaces entriesFloat16proposal:Math.f16roundDataView.prototype.getFloat16DataView.prototype.setFloat16es.namespace modules,/es/and/stable/namespaces entriesMath.clampstage 1 proposal:Math.clampMathextensions proposal, February 2025 TC39 meetingAsyncDisposableStackbug, tc39/proposal-explicit-resource-management/256DisposableStack,SuppressedErrorandIterator.prototype[@​@​dispose]marked as shipped from V8 ~ Chromium 134Error.isErroradded and marked as shipped from V8 ~ Chromium 134Math.f16roundandDataView.prototype.{ getFloat16, setFloat16 }marked as shipped from V8 ~ Chromium 135Iteratorhelpers proposal features marked as shipped from Safari 18.4JSON.parsesource text access proposal features marked as shipped from Safari 18.4Math.sumPrecisemarked as shipped from FF137v3.40.0Compare Source
Error.isErrorstage 3 proposal:Error.isError.shamIteratorsequencing stage 2.7 proposal:IteratorResultobjects when possible, tc39/proposal-iterator-sequencing/17, tc39/proposal-iterator-sequencing/18, December 2024 TC39 meetingSetmethodsDataView.prototype.{ getFloat16, setFloat16 }performance, #1379, thanks @LeviPesin%TypedArray%.prototype.toSplicedMath.scale) available on globalRegExp.escapemarked as shipped from Safari 18.2Promise.trymarked as shipped from Safari 18.2Math.f16roundandDataView.prototype.{ getFloat16, setFloat16 }marked as shipped from Safari 18.2Uint8Arrayto / from base64 and hex proposal methods marked as shipped from Safari 18.2JSON.parsesource text access proposal features marked as shipped from FF135RegExp.escapemarked as shipped from FF134Promise.trymarked as shipped from FF134Symbol.dispose,Symbol.asyncDisposeandIterator.prototype[@​@​dispose]marked as shipped from FF135JSON.parsesource text access proposal features marked as shipped from Bun 1.1.43URL.parsewas added - 22.1 instead of 22.0v3.39.0Compare Source
Iteratorhelpers proposal:IteratorIterator.fromIterator.prototype.dropIterator.prototype.everyIterator.prototype.filterIterator.prototype.findIterator.prototype.flatMapIterator.prototype.forEachIterator.prototype.mapIterator.prototype.reduceIterator.prototype.someIterator.prototype.takeIterator.prototype.toArrayIterator.prototype[@​@​toStringTag]es.namespace modules,/es/and/stable/namespaces entriesPromise.try:Promise.tryes.namespace module,/es/and/stable/namespaces entries/actual|full/promise/tryentries for the callback arguments supportMath.sumPreciseproposal:Math.sumPrecise/actual/namespace entries, unconditional forced replacement changed to feature detectionIteratorsequencing stage 2.7 proposal:Iterator.concatMapupsert stage 2 proposal:Map.prototype.getOrInsertMap.prototype.getOrInsertComputedWeakMap.prototype.getOrInsertWeakMap.prototype.getOrInsertComputed@@​speciespattern removed from%TypedArray%andArrayBuffermethods, tc39/ecma262/3450:%TypedArray%.prototype.filter%TypedArray%.prototype.filterReject%TypedArray%.prototype.map%TypedArray%.prototype.slice%TypedArray%.prototype.subarrayArrayBuffer.prototype.sliceUint8Arrayto / from base64 and hex proposal methods marked as shipped from FF133selfdescriptor is fixed in Deno 1.46.0Iteratorhelpers proposal methods marked as shipped from Bun 1.1.31v3.38.1Compare Source
URLSearchParamspercent decoding, #1357, #1361, thanks @slowcheetahIteratorhelpers proposal methods marked as shipped from FF131Math.f16roundandDataView.prototype.{ getFloat16, setFloat16 }marked as shipped from Bun 1.1.23RegExp.escapemarked as shipped from Bun 1.1.22Promise.trymarked as shipped from Bun 1.1.22Uint8Arrayto / from base64 and hex proposal methods marked as shipped from Bun 1.1.22v3.38.0Compare Source
RegExp.escapeproposal:RegExp.escape/actual/namespace entries, unconditional forced replacement changed to feature detectionPromise.tryproposal:Promise.try/actual/namespace entries, unconditional forced replacement changed to feature detectionUint8Arrayto / from base64 and hex stage 3 proposal:Uint8Array.fromBase64Uint8Array.fromHexUint8Array.prototype.setFromBase64Uint8Array.prototype.setFromHexUint8Array.prototype.toBase64Uint8Array.prototype.toHexUint8Array.prototype.{ setFromBase64, setFromHex }methodsUint8Array.fromBase64andUint8Array.prototype.setFromBase64lastChunkHandlingoption, proposal-arraybuffer-base64/33Uint8Array.prototype.toBase64omitPaddingoption, proposal-arraybuffer-base64/60TypeErroron arrays backed by detached buffersRegExpnamed capture groups polyfill in combination with non-capturing groups, #1352, thanks @Ulopprocess.getBuiltinModulefor getting built-in NodeJS modules where it's availablehttpsinstead ofhttpinURLconstructor feature detection to avoid extra notifications from some overly vigilant security scanners, #1345browserslistincore-js-compatdependencies that fixes an upstream issue with incorrect interpretation of somebrowserslistqueries, #1344, browserslist/829, browserslist/836Object.groupByandMap.groupByto work for non-objectsRangeErrorifSetmethods are called on an object with negative size propertySet.prototype.symmetricDifferenceto callthis.hasin each iterationArray.fromAsyncto not call theArrayconstructor twiceURL.parseMath.f16roundandDataView.prototype.{ getFloat16, setFloat16 }marked as shipped from FF129Symbol.asyncDisposeadded and marked as supported from V8 ~ Chromium 127Promise.tryadded and marked as supported from V8 ~ Chromium 128selfdescriptor is broken in Deno 1.45.3 (again)v3.37.1Compare Source
URL.parsefeature detection for some specific casesSetmethods proposal added and marked as supported from FF 127Symbol.disposeadded and marked as supported from V8 ~ Chromium 125Math.f16roundandDataView.prototype.{ getFloat16, setFloat16 }added and marked as supported from Deno 1.43URL.parseadded and marked as supported from Chromium 126URL.parseadded and marked as supported from NodeJS 22.0URL.parseadded and marked as supported from Deno 1.43v3.37.0Compare Source
Setmethods proposal:Set.prototype.intersectionSet.prototype.unionSet.prototype.differenceSet.prototype.symmetricDifferenceSet.prototype.isSubsetOfSet.prototype.isSupersetOfSet.prototype.isDisjointFromes.namespace modules,/es/and/stable/namespaces entriesMath.sumPrecisestage 2.7 proposal:Math.sumPrecisePromise.tryproposal:Promise.tryRegExp.escapestage 2 proposal:Symbol.customMatcherSymbol.customMatcherSymbol.customMatcherwell-known symbol from the pattern matching proposal is also used in the exactors proposal, added an entry also for this proposalURL.parse, url/825{ Object, Map }.groupBybug that does not support iterable primitivesArray.fromAsyncURL.parseadded and marked as supported from FF 126URL.parseadded and marked as supported from Bun 1.1.4URL.canParsefixed and marked as supported from Bun 1.1.0Setmethods fixed in JavaScriptCore and marked as supported from Bun 1.1.1v3.36.1Compare Source
Object.setPrototypeOf, #1329, thanks @minseok-choeArray.from, #1331, thanks @minseok-choequeueMicrotaskarityURL.canParsearity](https://redConfiguration
📅 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.