Closed renovate[bot] closed 11 months ago
:tada: This PR is included in version 3.0.0-next.43 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
:tada: This PR is included in version 3.0.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
This PR contains the following updates:
20.10.0
->20.10.4
3.33.3
->3.34.0
0.19.8
->0.19.9
9.0.0
->9.1.0
2.10.0
->2.11.1
23.0.0
->23.0.1
15.1.0
->15.2.0
1.40.0
->1.40.1
3.1.0
->3.1.1
Release Notes
zloirock/core-js (core-js)
### [`v3.34.0`](https://togithub.com/zloirock/core-js/blob/HEAD/CHANGELOG.md#3340---20231206) [Compare Source](https://togithub.com/zloirock/core-js/compare/v3.33.3...v3.34.0) - [`Array` grouping proposal](https://togithub.com/tc39/proposal-array-grouping): - Methods: - `Object.groupBy` - `Map.groupBy` - Moved to stable ES, [November 2023 TC39 meeting](https://togithub.com/tc39/proposal-array-grouping/issues/60) - Added `es.` namespace modules, `/es/` and `/stable/` namespaces entries - [`Promise.withResolvers` proposal](https://togithub.com/tc39/proposal-promise-with-resolvers): - Method: - `Promise.withResolvers` - Moved to stable ES, [November 2023 TC39 meeting](https://twitter.com/robpalmer2/status/1729216597623976407) - Added `es.` namespace module, `/es/` and `/stable/` namespaces entries - Fixed a web incompatibility issue of [`Iterator` helpers proposal](https://togithub.com/tc39/proposal-iterator-helpers), [proposal-iterator-helpers/287](https://togithub.com/tc39/proposal-iterator-helpers/pull/287) and some following changes, November 2023 TC39 meeting - Added [`Uint8Array` to / from base64 and hex stage 2 proposal](https://togithub.com/tc39/proposal-arraybuffer-base64): - Methods: - `Uint8Array.fromBase64` - `Uint8Array.fromHex` - `Uint8Array.prototype.toBase64` - `Uint8Array.prototype.toHex` - Relaxed some specific cases of [`Number.fromString`](https://togithub.com/tc39/proposal-number-fromstring) validation before clarification of [proposal-number-fromstring/24](https://togithub.com/tc39/proposal-number-fromstring/issues/24) - Fixed `@@toStringTag` property descriptors on DOM collections, [#1312](https://togithub.com/zloirock/core-js/issues/1312) - Fixed the order of arguments validation in `Array` iteration methods, [#1313](https://togithub.com/zloirock/core-js/issues/1313) - Some minor `atob` / `btoa` improvements - Compat data improvements: - [`Promise.withResolvers`](https://togithub.com/tc39/proposal-promise-with-resolvers) marked as shipped from FF121evanw/esbuild (esbuild)
### [`v0.19.9`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0199) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.8...v0.19.9) - Add support for transforming new CSS gradient syntax for older browsers The specification called [CSS Images Module Level 4](https://www.w3.org/TR/css-images-4/) introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now control the color space that the interpolation happens in as well as (for "polar" color spaces) control whether hue angle interpolation happens clockwise or counterclockwise. You can read more about this in [Mozilla's blog post about new CSS gradient features](https://developer.mozilla.org/en-US/blog/css-color-module-level-4/). With this release, esbuild will now automatically transform this syntax for older browsers in the `target` list. For example, here's a gradient that should appear as a rainbow in a browser that supports this new syntax: ```css /* Original code */ .rainbow-gradient { width: 100px; height: 100px; background: linear-gradient(in hsl longer hue, #7ff, #77f); } /* New output (with --target=chrome99) */ .rainbow-gradient { width: 100px; height: 100px; background: linear-gradient( #77ffff, #77ffaa 12.5%, #77ff80 18.75%, #84ff77 21.88%, #99ff77 25%, #eeff77 37.5%, #fffb77 40.62%, #ffe577 43.75%, #ffbb77 50%, #ff9077 56.25%, #ff7b77 59.38%, #ff7788 62.5%, #ff77dd 75%, #ff77f2 78.12%, #f777ff 81.25%, #cc77ff 87.5%, #7777ff); } ``` You can now use this syntax in your CSS source code and esbuild will automatically convert it to an equivalent gradient for older browsers. In addition, esbuild will now also transform "double position" and "transition hint" syntax for older browsers as appropriate: ```css /* Original code */ .stripes { width: 100px; height: 100px; background: linear-gradient(#e65 33%, #ff2 33% 67%, #99e 67%); } .glow { width: 100px; height: 100px; background: radial-gradient(white 10%, 20%, black); } /* New output (with --target=chrome33) */ .stripes { width: 100px; height: 100px; background: linear-gradient( #e65 33%, #ff2 33%, #ff2 67%, #99e 67%); } .glow { width: 100px; height: 100px; background: radial-gradient( #ffffff 10%, #aaaaaa 12.81%, #959595 15.62%, #7b7b7b 21.25%, #5a5a5a 32.5%, #444444 43.75%, #323232 55%, #161616 77.5%, #000000); } ``` You can see visual examples of these new syntax features by looking at [esbuild's gradient transformation tests](https://esbuild.github.io/gradient-tests/). If necessary, esbuild will construct a new gradient that approximates the original gradient by recursively splitting the interval in between color stops until the approximation error is within a small threshold. That is why the above output CSS contains many more color stops than the input CSS. Note that esbuild deliberately *replaces* the original gradient with the approximation instead of inserting the approximation before the original gradient as a fallback. The latest version of Firefox has multiple gradient rendering bugs (including incorrect interpolation of partially-transparent colors and interpolating non-sRGB colors using the incorrect color space). If esbuild didn't replace the original gradient, then Firefox would use the original gradient instead of the fallback the appearance would be incorrect in Firefox. In other words, the latest version of Firefox supports modern gradient syntax but interprets it incorrectly. - Add support for `color()`, `lab()`, `lch()`, `oklab()`, `oklch()`, and `hwb()` in CSS CSS has recently added lots of new ways of specifying colors. You can read more about this in [Chrome's blog post about CSS color spaces](https://developer.chrome.com/docs/css-ui/high-definition-css-color-guide). This release adds support for minifying colors that use the `color()`, `lab()`, `lch()`, `oklab()`, `oklch()`, or `hwb()` syntax and/or transforming these colors for browsers that don't support it yet: ```css /* Original code */ div { color: hwb(90deg 20% 40%); background: color(display-p3 1 0 0); } /* New output (with --target=chrome99) */ div { color: #669933; background: #ff0f0e; background: color(display-p3 1 0 0); } ``` As you can see, colors outside of the sRGB color space such as `color(display-p3 1 0 0)` are mapped back into the sRGB gamut and inserted as a fallback for browsers that don't support the new color syntax. - Allow empty type parameter lists in certain cases ([#3512](https://togithub.com/evanw/esbuild/issues/3512)) TypeScript allows interface declarations and type aliases to have empty type parameter lists. Previously esbuild didn't handle this edge case but with this release, esbuild will now parse this syntax: ```ts interface Foo<> {} type Bar<> = {} ``` This fix was contributed by [@magic-akari](https://togithub.com/magic-akari).prettier/eslint-config-prettier (eslint-config-prettier)
### [`v9.1.0`](https://togithub.com/prettier/eslint-config-prettier/blob/HEAD/CHANGELOG.md#Version-910-2023-12-02) [Compare Source](https://togithub.com/prettier/eslint-config-prettier/compare/v9.0.0...v9.1.0) - Added: \[unicorn/template-indent], (as a \[special rule]\[unicorn/template-indent-special]). Thanks to Gürgün Dayıoğlu ([@gurgunday](https://togithub.com/gurgunday))! - Changed: All the \[formatting rules that were deprecated in ESLint 8.53.0]\[deprecated-8.53.0] are now excluded if you set the `ESLINT_CONFIG_PRETTIER_NO_DEPRECATED` environment variable.ota-meshi/eslint-plugin-jsonc (eslint-plugin-jsonc)
### [`v2.11.1`](https://togithub.com/ota-meshi/eslint-plugin-jsonc/blob/HEAD/CHANGELOG.md#2111) [Compare Source](https://togithub.com/ota-meshi/eslint-plugin-jsonc/compare/v2.11.0...v2.11.1) ##### Patch Changes - [#283](https://togithub.com/ota-meshi/eslint-plugin-jsonc/pull/283) [`994983b`](https://togithub.com/ota-meshi/eslint-plugin-jsonc/commit/994983bf3d267a5afe43d3e93729be1d188eb1c7) Thanks [@ota-meshi](https://togithub.com/ota-meshi)! - fix: wrong report for object option in `jsonc/object-curly-spacing` ### [`v2.11.0`](https://togithub.com/ota-meshi/eslint-plugin-jsonc/blob/HEAD/CHANGELOG.md#2110) [Compare Source](https://togithub.com/ota-meshi/eslint-plugin-jsonc/compare/v2.10.0...v2.11.0) ##### Minor Changes - [#281](https://togithub.com/ota-meshi/eslint-plugin-jsonc/pull/281) [`c9e326e`](https://togithub.com/ota-meshi/eslint-plugin-jsonc/commit/c9e326e34bacb92707ad1c92a35c64ed9c34b73d) Thanks [@ota-meshi](https://togithub.com/ota-meshi)! - Improve compatibility with ESLint v9jsdom/jsdom (jsdom)
### [`v23.0.1`](https://togithub.com/jsdom/jsdom/blob/HEAD/Changelog.md#2301) [Compare Source](https://togithub.com/jsdom/jsdom/compare/23.0.0...23.0.1) - Fix incorrect `canvas` peer dependency.okonet/lint-staged (lint-staged)
### [`v15.2.0`](https://togithub.com/okonet/lint-staged/blob/HEAD/CHANGELOG.md#1520) [Compare Source](https://togithub.com/okonet/lint-staged/compare/v15.1.0...v15.2.0) ##### Minor Changes - [#1371](https://togithub.com/lint-staged/lint-staged/pull/1371) [`f3378be`](https://togithub.com/lint-staged/lint-staged/commit/f3378be894fb84800341800b1e4f6f8bc8dfd904) Thanks [@iiroj](https://togithub.com/iiroj)! - Using the `--no-stash` flag no longer discards all unstaged changes to partially staged files, which resulted in inadvertent data loss. This fix is available with a new flag `--no-hide-partially-staged` that is automatically enabled when `--no-stash` is used. ##### Patch Changes - [#1362](https://togithub.com/lint-staged/lint-staged/pull/1362) [`17bc480`](https://togithub.com/lint-staged/lint-staged/commit/17bc480c0f8767407a87527931558de8d1d1551d) Thanks [@antonk52](https://togithub.com/antonk52)! - update lilconfig@3.0.0 - [#1368](https://togithub.com/lint-staged/lint-staged/pull/1368) [`7c55ca9`](https://togithub.com/lint-staged/lint-staged/commit/7c55ca9f410043016e8b33b3b523b9b7e764acf4) Thanks [@iiroj](https://togithub.com/iiroj)! - Update most dependencies - [#1368](https://togithub.com/lint-staged/lint-staged/pull/1368) [`777d4e9`](https://togithub.com/lint-staged/lint-staged/commit/777d4e976852af4c181ffbe055f3531343349695) Thanks [@iiroj](https://togithub.com/iiroj)! - To improve performance, only use `lilconfig` when searching for config files outside the git repo. In the regular case, *lint-staged* finds the config files from the Git index and loads them directly. - [#1373](https://togithub.com/lint-staged/lint-staged/pull/1373) [`85eb0dd`](https://togithub.com/lint-staged/lint-staged/commit/85eb0ddab1eba0c0bcc8cc109e17dc2bbb3d044e) Thanks [@iiroj](https://togithub.com/iiroj)! - When determining git directory, use `fs.realpath()` only for symlinks. It looks like `fs.realpath()` changes some Windows mapped network filepaths unexpectedly, causing issues.microsoft/playwright (playwright)
### [`v1.40.1`](https://togithub.com/microsoft/playwright/releases/tag/v1.40.1) [Compare Source](https://togithub.com/microsoft/playwright/compare/v1.40.0...v1.40.1) ##### Highlights [https://github.com/microsoft/playwright/issues/28319](https://togithub.com/microsoft/playwright/issues/28319) - \[REGRESSION]: Version 1.40.0 Produces corrupted traces[https://github.com/microsoft/playwright/issues/28371](https://togithub.com/microsoft/playwright/issues/28371)1 - \[BUG] The color of the 'ok' text did not change to green in the vs code test results sectio[https://github.com/microsoft/playwright/issues/28321](https://togithub.com/microsoft/playwright/issues/28321)21 - \[BUG] Ambiguous test outcome and status for serial mo[https://github.com/microsoft/playwright/issues/28362](https://togithub.com/microsoft/playwright/issues/28362)362 - \[BUG] Merging blobs ends up in Error: Cannot create a string longer than 0x1fffffe8 charact[https://github.com/microsoft/playwright/pull/28239](https://togithub.com/microsoft/playwright/pull/28239)8239 - fix: collect all errors in removeFolders ##### Browser Versions - Chromium 120.0.6099.28 - Mozilla Firefox 119.0 - WebKit 17.4 This version was also tested against the following stable channels: - Google Chrome 119 - Microsoft Edge 119prettier/prettier (prettier)
### [`v3.1.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#311) [Compare Source](https://togithub.com/prettier/prettier/compare/3.1.0...3.1.1) [diff](https://togithub.com/prettier/prettier/compare/3.1.0...3.1.1) ##### Fix config file search ([#15363](https://togithub.com/prettier/prettier/pull/15363) by [@fisker](https://togithub.com/fisker)) Previously, we start search for config files from the filePath as a directory, if it happened to be a directory and contains config file, it will be used by mistake. ```text ├─ .prettierrc └─ test.js (A directory) └─ .prettierrc ``` ```js // Prettier 3.1.0 await prettier.resolveConfigFile(new URL("./test.js", import.meta.url)); //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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.