chore(deps): update all non-major dependencies #12
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
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
2 times, most recently
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
4 times, most recently
from
95f2273
to
737bf2f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
737bf2f
to
49dd27d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
650eada
to
1dd4a0e
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
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
1dd4a0e
to
acb137a
Compare
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.
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
acb137a
to
591aa05
Compare
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.
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
591aa05
to
afa7bd6
Compare
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
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
1b41bf1
to
8bd2eb6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
8bd2eb6
to
2f724ae
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
2f724ae
to
e2b2c9e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
e2b2c9e
to
2672be5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
2672be5
to
6c6089f
Compare
This PR contains the following updates:
^0.7.1->^0.7.22.2.0->2.3.03.25.1->3.39.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.0^1.7->^1.12.0^11.1->^11.6.0^0.13.0->^0.14.32.15.8->2.18.18.4.16->8.4.49Release Notes
nuxt/image (@nuxt/image)
v0.7.2Compare Source
composer/installers (composer/installers)
v2.3.0Compare Source
What's Changed
Full Changelog: composer/installers@v2.2.0...v2.3.0
zloirock/core-js (core-js)
v3.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.canParsearitySuppressedErrorextra arguments support and arityvalueargument ofURLSearchParams.prototype.{ has, delete }marked as supported from Bun 1.0.31Array.prototype.{ toSpliced, toReversed, with }andatobmarked as supportedv3.36.0Compare Source
ArrayBuffer.prototype.transferand friends proposal:ArrayBuffer.prototype.detachedArrayBuffer.prototype.transferArrayBuffer.prototype.transferToFixedLengthes.namespace modules,/es/and/stable/namespaces entriesUint8Arrayto / from base64 and hex proposal:Uint8Array.fromBase64Uint8Array.fromHexUint8Array.prototype.toBase64Uint8Array.prototype.toHex/actual/namespace entriesPromise.tryproposal has been resurrected and moved to stage 2, Febrary 2024 TC39 meetingcore-js/stage/2.7- still emptySet.prototype.intersectionfeature detectionArray.prototype.{ indexOf, lastIndexOf, includes }, #1325, thanks @minseok-choeArray.prototype.{ reduce, reduceRight }, #1327, thanks @minseok-choeArray.fromand some other methods with proxy targets, #1322, thanks @minseok-choeArrayBuffer.prototype.transferand friends proposal in some specific cases in IE10-Date.prototype.toJSONtoJSON.stringifyentries dependencies{ Map, Object }.groupBy,Promise.withResolvers,ArrayBuffer.prototype.transferand friends marked as supported from Safari 17.4Setmethods fixed and marked as supported from V8 ~ Chrome 123Symbol.metadatamarked as supported from Deno 1.40.4v3.35.1Compare Source
ToLengthoperation with bigints, #1318String#splitpolyfillIteratorhelpers proposal methods marked as supported from V8 ~ Chrome 122Setmethods, but they have a bug similar to Safariselfmarked as fixed from Bun 1.0.22SuppressedErrorandSymbol.{ dispose , asyncDispose }marked as supported from Bun 1.0.23v3.35.0Compare Source
{ Map, Set, WeakMap, WeakSet }.{ from, of }became non-generic, following this and some other notes. Now they can be invoked withoutthis, but no longer return subclass instancesSymbolpolyfillqueueMicrotaskpolyfillArrayBufferArray.fromAsyncmarked as supported from V8 ~ Chrome 121Array.prototype.pushbug is fixed in V8 ~ Chrome 122 (Hallelujah!)ArrayBuffer.prototype.transferand friends proposal features marked as supported from FF 122 and Bun 1.0.19Object.groupByandMap.groupBymarked as supported from Bun 1.0.19Iteratorhelpers proposal methods are still not disabled in Deno, the web compatibility issue why it was disabled in Chromium makes no sense for Deno and fixed in the spec, they marked as supported from Deno 1.37v3.34.0Compare Source
Arraygrouping proposal:Object.groupByMap.groupByes.namespace modules,/es/and/stable/namespaces entriesPromise.withResolversproposal:Promise.withResolverses.namespace module,/es/and/stable/namespaces entriesIteratorhelpers proposal, proposal-iterator-helpers/287 and some following changes, November 2023 TC39 meetingUint8Arrayto / from base64 and hex stage 2 proposal:Uint8Array.fromBase64Uint8Array.fromHexUint8Array.prototype.toBase64Uint8Array.prototype.toHexNumber.fromStringvalidation before clarification of proposal-number-fromstring/24@@​toStringTagproperty descriptors on DOM collections, #1312Arrayiteration methods, #1313atob/btoaimprovementsPromise.withResolversmarked as shipped from FF121v3.33.3Compare Source
[[DedentMap]]fromString.dedentproposal betweencore-jsinstances before stabilization of the proposalArray.fromAsyncmarked as supported from Deno 1.38Symbol.{ dispose, asyncDispose }marked as supported from Deno 1.38v3.33.2Compare Source
structuredClonepolyfill, avoided second tree pass in cases of transferringSuppressedErrortostructuredClonepolyfillArrayBufferandDataViewdependencies ofstructuredClonelack of which could cause errors in some entries in IE10-Number.fromStringURL.canParsemarked as supported from Chromium 120v3.33.1Compare Source
Symbolpolyfill on global object, #1289type: commonjsinpackage.jsonof all packages to avoid potential breakage in future Node versions, see this issueString.prototype.{ isWellFormed, toWellFormed }marked as supported from FF119v3.33.0Compare Source
RegExpescaping stage 2 proposal, September 2023 TC39 meeting:RegExp.escapemethod with the new set of symbols for escapingcore-js, but it was removed after rejecting the old version of this proposalArrayBuffer.prototype.{ transfer, transferToFixedLength }and support transferring ofArrayBuffers viastructuredCloneto engines withMessageChannelMath.f16roundpolyfillMath.f16roundandDataView.prototype.{ getFloat16, setFloat16 }Observableproposal because of incompatibility with the new WHATWGObservableproposalSymbolpolyfill, #1289Iteratorhelpers because of some Web compatibility issuesPromise.withResolversmarked as supported from V8 ~ Chrome 119Arraygrouping proposal features marked as supported from FF119valueargument ofURLSearchParams.prototype.{ has, delete }marked as properly supported from V8 ~ Chrome 118URL.canParseandURLSearchParams.prototype.sizemarked as supported from Bun 1.0.2v3.32.2Compare Source
structuredClonefeature detection[email protected]bug, #1288evalbug, #1287v3.32.1Compare Source
processpolyfill tocore-jsvia some bundlers oresm.sh, #1277Promise.withResolversmarked as supported from Bun 0.7.1v3.32.0Compare Source
Arraygrouping proposal, July 2023 TC39 meeting updates:/actual/namespaces entries, unconditional forced replacement changed to feature detectionPromise.withResolversproposal, July 2023 TC39 meeting updates:/actual/namespaces entries, unconditional forced replacement changed to feature detectionSetmethods stage 3 proposal, July 2023 TC39 meeting updates:Setsizes, proposal-set-methods/88IsCallablecheck inGetKeysIterator, proposal-set-methods/101Stringwrapper objects, July 2023 TC39 meeting update, proposal-iterator-helpers/281Iteratoris not constructible from the active function object (works as an abstract class)/actual/namespace entries, unconditional forced replacement changed to feature detection[@@​dispose]()method when hint isasync-dispose, proposal-explicit-resource-management/180Float16Arraystage 3 proposal:Float16Arrayright now, however, make sense to add some methods from this proposal.Math.f16roundDataView.prototype.getFloat16DataView.prototype.setFloat16DataViewget / setUint8Clampedmethods stage 1 proposal:DataView.prototype.getUint8ClampedDataView.prototype.setUint8Clampedvalueargument ofURLSearchParams.prototype.{ has, delete }Setmethods implementation by the actual specSymbol.{ dispose, asyncDispose }descriptors from NodeJS 20.4 / transpilers helpers / userland codeAsyncIteratorPrototypecore-js/configuratoroption, #1268Iteratorhelpers proposal features marked as supported from V8 ~ Chrome 117Arraygrouping proposal features marked as supported from V8 ~ Chrome 117Symbol.{ dispose, asyncDispose }as supported from NodeJS 20.5.0 (as mentioned above, NodeJS 20.4.0 add it, but with incorrect descriptors)v3.31.1Compare Source
structuredClonebug with cloning views of transferred buffers, #1265DataViewmethodsFloat16ArrayinstructuredCloneSetmethods proposal marked as supported from Safari 17.0URLfeatures:URL.canParse,URLSearchParams.prototype.sizeandvalueargument ofURLSearchParams.prototype.{ has, delete }marked as supported from Safari 17.0valueargument ofURLSearchParams.prototype.{ has, delete }marked as supported from Deno 1.35AggregateErrorand well-formedJSON.stringifymarked as supported React Native 0.72 Hermesv3.31.0Compare Source
String.prototype.isWellFormedmethodString.prototype.toWellFormedmethodes.namespace modules,/es/and/stable/namespaces entriesArraygrouping proposal, May 2023 TC39 meeting updates:Object.groupBymethodMap.groupBymethod (with the actual semantic - with a minor difference it was present in the collections methods stage 1 proposal)Function.prototype[Symbol.metadata](=== null)/actual/entriesSymbol.iteratorfallback from callable check toundefined/nullcheck, May 2023 TC39 meeting, proposal-iterator-helpers/272IsCallablecheck onNextMethod, deferring errors toCallsite, May 2023 TC39 meeting, proposal-iterator-helpers/274Promise.withResolversstage 2 proposal:Promise.withResolversmethodSymbolpredicates stage 2 proposal:Symbol, May 2023 TC39 meeting:Symbol.isRegistered->Symbol.isRegisteredSymbolmethodSymbol.isWellKnown->Symbol.isWellKnownSymbolmethodvalueargument ofURLSearchParams.prototype.{ has, delete }, url/735ArrayBuffer.prototype.{ transfer, transferToFixedLength }polyfillsAsyncDisposableStack.prototype.adoptcallback, #1258URLSearchParams#sizein ES3 engines (IE8-)Object.{ entries, values }for some IE versions bug with invisible integer keys onnull-prototype objectscore-js-compat, #1235, thanks @susnuxSet.prototype.differencethat was missed in Bun because of a bug added inConfiguration
📅 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.