timdeschryver / timdeschryver.dev

https://timdeschryver.dev
55 stars 30 forks source link

chore(deps): update all #300

Closed renovate[bot] closed 10 months ago

renovate[bot] commented 10 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sveltejs/kit (source) 1.27.7 -> 1.30.3 age adoption passing confidence
esbuild 0.19.8 -> 0.19.9 age adoption passing confidence
prettier (source) 3.1.0 -> 3.1.1 age adoption passing confidence

Release Notes

sveltejs/kit (@​sveltejs/kit) ### [`v1.30.3`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1303) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.30.2...@sveltejs/kit@1.30.3) ##### Patch Changes - fix: correct documentation for beforeNavigate ([#​11300](https://togithub.com/sveltejs/kit/pull/11300)) ### [`v1.30.2`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1302) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.30.1...@sveltejs/kit@1.30.2) ##### Patch Changes - fix: revert recent 'correctly return 415' and 'correctly return 404' changes ([#​11295](https://togithub.com/sveltejs/kit/pull/11295)) ### [`v1.30.1`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1301) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.30.0...@sveltejs/kit@1.30.1) ##### Patch Changes - fix: prerendered root page with `paths.base` config uses correct trailing slash option ([#​10763](https://togithub.com/sveltejs/kit/pull/10763)) - fix: correctly return 404 when a form action is not found ([#​11278](https://togithub.com/sveltejs/kit/pull/11278)) ### [`v1.30.0`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1300) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.29.1...@sveltejs/kit@1.30.0) ##### Minor Changes - feat: inline `response.arrayBuffer()` during ssr ([#​10535](https://togithub.com/sveltejs/kit/pull/10535)) ##### Patch Changes - fix: allow `"false"` value for preload link options ([#​10555](https://togithub.com/sveltejs/kit/pull/10555)) - fix: call worker `unref` instead of `terminate` ([#​10120](https://togithub.com/sveltejs/kit/pull/10120)) - fix: correctly analyse exported server API methods during build ([#​11019](https://togithub.com/sveltejs/kit/pull/11019)) - fix: avoid error when back navigating before page is initialized ([#​10636](https://togithub.com/sveltejs/kit/pull/10636)) - fix: allow service-worker.js to import assets ([#​9285](https://togithub.com/sveltejs/kit/pull/9285)) - fix: distinguish better between not-found and internal-error ([#​11131](https://togithub.com/sveltejs/kit/pull/11131)) ### [`v1.29.1`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1291) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.29.0...@sveltejs/kit@1.29.1) ##### Patch Changes - fix: correctly return 415 when unexpected content types are submitted to actions ([#​11255](https://togithub.com/sveltejs/kit/pull/11255)) - chore: deprecate `preloadCode` calls with multiple arguments ([#​11266](https://togithub.com/sveltejs/kit/pull/11266)) ### [`v1.29.0`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1290) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.28.0...@sveltejs/kit@1.29.0) ##### Minor Changes - feat: add `resolveRoute` to `$app/paths`, deprecate `resolvePath` ([#​11261](https://togithub.com/sveltejs/kit/pull/11261)) ### [`v1.28.0`](https://togithub.com/sveltejs/kit/blob/HEAD/packages/kit/CHANGELOG.md#1280) [Compare Source](https://togithub.com/sveltejs/kit/compare/@sveltejs/kit@1.27.7...@sveltejs/kit@1.28.0) ##### Minor Changes - chore: deprecate top level promise await behaviour ([#​11175](https://togithub.com/sveltejs/kit/pull/11175)) ##### Patch Changes - fix: resolve relative cookie paths before storing ([#​11253](https://togithub.com/sveltejs/kit/pull/11253)) - chore: deprecate cookies.set/delete without path option ([#​11237](https://togithub.com/sveltejs/kit/pull/11237)) - fix: make sure promises from fetch handle errors ([#​11228](https://togithub.com/sveltejs/kit/pull/11228))
evanw/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/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)); // /test.js/.prettierrc // Prettier 3.1.1 await prettier.resolveConfigFile(new URL("./test.js", import.meta.url)); // /.prettierrc ``` ##### Skip explicitly passed symbolic links with `--no-error-on-unmatched-pattern` ([#​15533](https://togithub.com/prettier/prettier/pull/15533) by [@​sanmai-NL](https://togithub.com/sanmai-NL)) Since Prettier v3, we stopped following symbolic links, however in some use cases, the symbolic link patterns can't be filtered out, and there is no way to prevent Prettier from throwing errors. In Prettier 3.1.1, you can use `--no-error-on-unmatched-pattern` to simply skip symbolic links. ##### Consistently use tabs in ternaries when `useTabs` is `true` ([#​15662](https://togithub.com/prettier/prettier/pull/15662) by [@​auvred](https://togithub.com/auvred)) ```jsx // Input aaaaaaaaaaaaaaa ? bbbbbbbbbbbbbbbbbb : ccccccccccccccc ? ddddddddddddddd : eeeeeeeeeeeeeee ? fffffffffffffff : gggggggggggggggg; // Prettier 3.1.0 aaaaaaaaaaaaaaa ? bbbbbbbbbbbbbbbbbb : ccccccccccccccc ? ddddddddddddddd : eeeeeeeeeeeeeee ? fffffffffffffff : gggggggggggggggg; // Prettier 3.1.1 aaaaaaaaaaaaaaa ? bbbbbbbbbbbbbbbbbb : ccccccccccccccc ? ddddddddddddddd : eeeeeeeeeeeeeee ? fffffffffffffff : gggggggggggggggg; ``` ##### Improve config file search ([#​15663](https://togithub.com/prettier/prettier/pull/15663) by [@​fisker](https://togithub.com/fisker)) The Prettier config file search performance has been improved by more effective cache strategy. ##### Fix unstable and ugly formatting for comments in destructuring patterns ([#​15708](https://togithub.com/prettier/prettier/pull/15708) by [@​sosukesuzuki](https://togithub.com/sosukesuzuki)) ```tsx // Input const { foo, // bar // baz }: Foo = expr; // Prettier 3.1.0 const { foo1, } // bar // baz : Foo = expr; // Prettier 3.1.0 second output const { foo1, // bar } // baz : Foo = expr; // Prettier 3.1.1 const { foo1, // bar // baz }: Foo = expr; ``` ##### Support "Import Attributes" ([#​15718](https://togithub.com/prettier/prettier/pull/15718) by [@​fisker](https://togithub.com/fisker)) [TypeScript 5.3](https://devblogs.microsoft.com/typescript/announcing-typescript-5-3/#import-attributes) supports the latest updates to the [import attributes](https://togithub.com/tc39/proposal-import-attributes) proposal. ```tsx import something from "./something.json" with { type: "json" }; ``` ##### Fix false claim in docs that cursorOffset is incompatible with rangeStart/rangeEnd ([#​15750](https://togithub.com/prettier/prettier/pull/15750) by [@​ExplodingCabbage](https://togithub.com/ExplodingCabbage)) The cursorOffset option has in fact been compatible with rangeStart/rangeEnd for over 5 years, thanks to work by [@​ds300](https://togithub.com/ds300). However, Prettier's documentation (including the CLI `--help` text) continued to claim otherwise, falsely. The documentation is now fixed. ##### Keep curly braces and `from` keyword in empty `import` statements ([#​15756](https://togithub.com/prettier/prettier/pull/15756) by [@​fisker](https://togithub.com/fisker)) ```js // Input import { } from 'foo'; import { /* comment */ } from 'bar'; // Prettier 3.1.0 import {} from "foo"; import /* comment */ "bar"; // Prettier 3.1.1 import {} from "foo"; import {} from /* comment */ "bar"; ``` ##### Keep empty import attributes and assertions ([#​15757](https://togithub.com/prettier/prettier/pull/15757) by [@​fisker](https://togithub.com/fisker)) ```js // Input import foo from "foo" with {}; import bar from "bar" assert {}; // Prettier 3.1.0 import foo from "foo"; import bar from "bar"; // Prettier 3.1.1 import foo from "foo" with {}; import bar from "bar" assert {}; ```

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" in timezone Europe/Brussels, 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.

github-actions[bot] commented 10 months ago

Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-rock-0fb035b03-300.westeurope.1.azurestaticapps.net

github-actions[bot] commented 10 months ago

Azure Static Web Apps: Your stage site is ready! Visit it here: https://salmon-rock-0fb035b03-300.westeurope.1.azurestaticapps.net