chore(deps): update all non-major dependencies

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@commitlint/cli (source)	`18.4.2` -> `18.4.3`
@commitlint/config-conventional (source)	`18.4.2` -> `18.4.3`
@nuxt/webpack-builder (source)	`3.8.1` -> `3.8.2`
@types/node (source)	`20.9.1` -> `20.9.3`
commitlint (source)	`18.4.2` -> `18.4.3`
core-js	`3.33.2` -> `3.33.3`
esbuild	`0.19.5` -> `0.19.7`
nuxt (source)	`3.8.1` -> `3.8.2`
stylelint-config-recess-order	`4.3.0` -> `4.4.0`
vitepress (source)	`1.0.0-rc.28` -> `1.0.0-rc.29`

Release Notes

conventional-changelog/commitlint (@commitlint/cli)

### [`v18.4.3`](https://togithub.com/conventional-changelog/commitlint/blob/HEAD/@commitlint/cli/CHANGELOG.md#1843-2023-11-21) [Compare Source](https://togithub.com/conventional-changelog/commitlint/compare/v18.4.2...v18.4.3) **Note:** Version bump only for package [@commitlint/cli](https://togithub.com/commitlint/cli)

conventional-changelog/commitlint (@commitlint/config-conventional)

### [`v18.4.3`](https://togithub.com/conventional-changelog/commitlint/blob/HEAD/@commitlint/config-conventional/CHANGELOG.md#1843-2023-11-21) [Compare Source](https://togithub.com/conventional-changelog/commitlint/compare/v18.4.2...v18.4.3) **Note:** Version bump only for package [@commitlint/config-conventional](https://togithub.com/commitlint/config-conventional)

nuxt/nuxt (@nuxt/webpack-builder)

### [`v3.8.2`](https://togithub.com/nuxt/nuxt/releases/tag/v3.8.2) [Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.8.1...v3.8.2) > 3.8.2 is a patch release focusing on bug fixes #### 👀 Highlights 3.8.2 is a patch release and we've deferred some exciting features in our next release (3.9.0, expected in December) but it does bring a significant [Nitro minor release: v2.8.0](https://togithub.com/unjs/nitro/releases/tag/v2.8.0). It's well worth checking out the release notes. 👉 Note that as Nitro has updated to rollup v4, but as Nuxt's vite dependency is still on rollup v3 until v3.9, you may experience type mismatches in modules or your projects if you are dependent on particular rollup plugins or plugin types. #### ✅ Upgrading As usual, our recommendation for upgrading is to run: ```sh nuxi upgrade --force ``` This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem. #### 👉 Changelog [compare changes](https://togithub.com/nuxt/nuxt/compare/v3.8.1...v3.8.2) ##### 🩹 Fixes - **vite:** Skip warming up node builtins ([#24162](https://togithub.com/nuxt/nuxt/pull/24162)) - **vite:** Provide default values for `transformAssetUrls` ([#24173](https://togithub.com/nuxt/nuxt/pull/24173)) - **nuxt:** Wrap caught asyncData error in `createError` ([#24093](https://togithub.com/nuxt/nuxt/pull/24093)) - **nuxt:** Include plugin templates in `plugins.d.ts` if they will be written ([#23943](https://togithub.com/nuxt/nuxt/pull/23943)) - **nuxt:** Handle multi-line slots in islands ([#24212](https://togithub.com/nuxt/nuxt/pull/24212)) - **nuxt:** Fix replace regex used for slots in islands SSR ([#24255](https://togithub.com/nuxt/nuxt/pull/24255)) - **vite:** Use rollup replace plugin for `typeof` optimisations ([#23903](https://togithub.com/nuxt/nuxt/pull/23903)) - **nuxt:** Provide route component names to `KeepAlive` cache ([#24024](https://togithub.com/nuxt/nuxt/pull/24024)) - **schema:** Use scule types for `runtimeConfig` type hints ([#23696](https://togithub.com/nuxt/nuxt/pull/23696)) - **nuxt:** Deeply unwrap headers/query for `useFetch` key ([#24307](https://togithub.com/nuxt/nuxt/pull/24307)) - **nuxt:** Split component name case in each segment ([#24318](https://togithub.com/nuxt/nuxt/pull/24318)) - **nuxt:** Do not compute `useFetch` key from headers ([#23462](https://togithub.com/nuxt/nuxt/pull/23462), [#24333](https://togithub.com/nuxt/nuxt/pull/24333)) - **nuxt:** Set framework info for nitro ([#24340](https://togithub.com/nuxt/nuxt/pull/24340)) - **schema:** Add type for `ignoreOptions` ([#24337](https://togithub.com/nuxt/nuxt/pull/24337)) - **nuxt:** Log errors rendering islands ([#24356](https://togithub.com/nuxt/nuxt/pull/24356)) - **nuxt:** Respect custom timeout in `useFetch` ([#24364](https://togithub.com/nuxt/nuxt/pull/24364)) - **nuxt:** Use max length + iterations for `useCookie` timeout ([#24253](https://togithub.com/nuxt/nuxt/pull/24253)) - **nuxt:** Handle errors when booting app with `app:error` ([#24376](https://togithub.com/nuxt/nuxt/pull/24376)) ##### 📖 Documentation - Remove unused import from example ([#24168](https://togithub.com/nuxt/nuxt/pull/24168)) - Create a page explaining `import.meta` ([#24186](https://togithub.com/nuxt/nuxt/pull/24186)) - Remove link to `.nuxtrc` in `nuxt/starter` ([56147b4a8](https://togithub.com/nuxt/nuxt/commit/56147b4a8)) - Correct spelling from "opiniated" to "opinionated" ([#24248](https://togithub.com/nuxt/nuxt/pull/24248)) - Mention new `defineNuxtPlugin` syntax in bridge migration ([#23036](https://togithub.com/nuxt/nuxt/pull/23036)) - Mention `nuxt3-vuex-module` in migration guide ([#24260](https://togithub.com/nuxt/nuxt/pull/24260)) - Fix links to other auto-imports pages ([#24269](https://togithub.com/nuxt/nuxt/pull/24269)) - Remove only ([#24295](https://togithub.com/nuxt/nuxt/pull/24295)) - Update link to deno deploy provider docs ([88ee7b7ea](https://togithub.com/nuxt/nuxt/commit/88ee7b7ea)) - Typos and wording tweaks for getting started section ([#24319](https://togithub.com/nuxt/nuxt/pull/24319)) - Update `.gitignore` in directory structure ([#24338](https://togithub.com/nuxt/nuxt/pull/24338)) - Add hint about `app.config` placement with custom `srcDir` ([#24252](https://togithub.com/nuxt/nuxt/pull/24252)) - Typos and wording tweaks for guide section ([#24323](https://togithub.com/nuxt/nuxt/pull/24323)) - Remove path for `` in example ([#24244](https://togithub.com/nuxt/nuxt/pull/24244)) - Mention changing directory in installation guide ([#23680](https://togithub.com/nuxt/nuxt/pull/23680)) - Use `@nuxt/kit-nightly` in example ([bdedc3207](https://togithub.com/nuxt/nuxt/commit/bdedc3207)) - Update `nuxi-edge` to `nuxi-nightly` ([#24347](https://togithub.com/nuxt/nuxt/pull/24347)) - Minor wording & formatting tweaks ([#24349](https://togithub.com/nuxt/nuxt/pull/24349)) - Add AWS Amplify Hosting to hosting providers ([#24371](https://togithub.com/nuxt/nuxt/pull/24371)) - Fix typo ([#24375](https://togithub.com/nuxt/nuxt/pull/24375)) - Simplify to deployments page ([13b93237e](https://togithub.com/nuxt/nuxt/commit/13b93237e)) - Update to /deploy url ([751dad7d7](https://togithub.com/nuxt/nuxt/commit/751dad7d7)) - Improve readme ([07ab072bc](https://togithub.com/nuxt/nuxt/commit/07ab072bc)) ##### 🏡 Chore - Extract `@nuxt/test-utils` to separate repo ([#24146](https://togithub.com/nuxt/nuxt/pull/24146)) - Remove stray router.options file ([7fbcaf290](https://togithub.com/nuxt/nuxt/commit/7fbcaf290)) - Fix `repository` fields in `package.json` ([54529c17d](https://togithub.com/nuxt/nuxt/commit/54529c17d)) - Add homepage and repo directory to `package.json`s ([#24189](https://togithub.com/nuxt/nuxt/pull/24189)) - Update to use `@nuxt/eslint-config` ([#24209](https://togithub.com/nuxt/nuxt/pull/24209)) - Revert coverage provider version ([b90b631df](https://togithub.com/nuxt/nuxt/commit/b90b631df)) ##### ✅ Tests - Add route-provider e2e test ([#24195](https://togithub.com/nuxt/nuxt/pull/24195)) - **nuxt:** Add additional unit tests for composables ([#24289](https://togithub.com/nuxt/nuxt/pull/24289)) ##### ❤️ Contributors - Anthony Fu ([@antfu](https://togithub.com/antfu)) - Sébastien Chopin ([@Atinux](https://togithub.com/Atinux)) - Christian Gil ([@ChrisGV04](https://togithub.com/ChrisGV04)) - Clément Ollivier ([@clemcode](https://togithub.com/clemcode)) - Luke Nelson ([@luc122c](https://togithub.com/luc122c)) - Siegerts ([@siegerts](https://togithub.com/siegerts)) - Julien Huang ([@huang-julien](https://togithub.com/huang-julien)) - Joe Hawes ([@morehawes](https://togithub.com/morehawes)) - Alexander Lichter ([@manniL](https://togithub.com/manniL)) - Daniel Roe ([@danielroe](https://togithub.com/danielroe)) - Damian Głowala ([@DamianGlowala](https://togithub.com/DamianGlowala)) - Pooya Parsa ([@pi0](https://togithub.com/pi0)) - Boby Tiwari ([@Boby900](https://togithub.com/Boby900)) - Sita ([@Pitabread8](https://togithub.com/Pitabread8)) - Nils Wiesinger ([@warflash](https://togithub.com/warflash)) - Webfansplz ([@webfansplz](https://togithub.com/webfansplz)) - Aaron_Zhou ([@Clarkkkk](https://togithub.com/Clarkkkk)) - 56 ([@Nationalcat](https://togithub.com/Nationalcat)) - Adrien Zaganelli ([@adrienZ](https://togithub.com/adrienZ)) - Alonge Akintomide ([@tomidealonge](https://togithub.com/tomidealonge)) - Nasser BOUKEHIL ([@nasrob](https://togithub.com/nasrob)) - Passionate-bram ([@passionate-bram](https://togithub.com/passionate-bram)) - Maxime Pauvert ([@maximepvrt](https://togithub.com/maximepvrt)) - Dario Ferderber ([@darioferderber](https://togithub.com/darioferderber)) - Brendan Mulholland ([@bmulholland](https://togithub.com/bmulholland))

conventional-changelog/commitlint (commitlint)

### [`v18.4.3`](https://togithub.com/conventional-changelog/commitlint/blob/HEAD/@alias/commitlint/CHANGELOG.md#1843-2023-11-21) [Compare Source](https://togithub.com/conventional-changelog/commitlint/compare/v18.4.2...v18.4.3) **Note:** Version bump only for package commitlint

zloirock/core-js (core-js)

### [`v3.33.3`](https://togithub.com/zloirock/core-js/blob/HEAD/CHANGELOG.md#3333---20231120) [Compare Source](https://togithub.com/zloirock/core-js/compare/v3.33.2...v3.33.3) - Fixed an issue getting the global object on Duktape, [#1303](https://togithub.com/zloirock/core-js/issues/1303) - Avoid sharing internal `[[DedentMap]]` from [`String.dedent` proposal](https://togithub.com/tc39/proposal-string-dedent) between `core-js` instances before stabilization of the proposal - Some internal untangling - Compat data improvements: - Added [Deno 1.38](https://deno.com/blog/v1.38) compat data mapping - [`Array.fromAsync`](https://togithub.com/tc39/proposal-array-from-async) marked as [supported from Deno 1.38](https://togithub.com/denoland/deno/pull/21048) - [`Symbol.{ dispose, asyncDispose }`](https://togithub.com/tc39/proposal-explicit-resource-management) marked as [supported from Deno 1.38](https://togithub.com/denoland/deno/pull/20845) - Added Opera Android 79 compat data mapping - Added Oculus Quest Browser 30 compat data mapping - Updated Electron 28 and 29 compat data mapping

evanw/esbuild (esbuild)

### [`v0.19.7`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0197) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.6...v0.19.7) - Add support for bundling code that uses import attributes ([#3384](https://togithub.com/evanw/esbuild/issues/3384)) JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far): 1. Import assertions (deprecated, will not be standardized) - Uses the `assert` keyword - Does *not* affect module resolution - Causes an error if the assertion fails - Shipping in Chrome 91+ (and in esbuild 0.11.22+) 2. Import attributes (currently set to become standardized) - Uses the `with` keyword - Affects module resolution - Unknown attributes cause an error - Shipping in node 21+ You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports). With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming [JSON module standard](https://togithub.com/tc39/proposal-json-modules): ```js // On static imports import foo from './package.json' with { type: 'json' } console.log(foo) // On dynamic imports const bar = await import('./package.json', { with: { type: 'json' } }) console.log(bar) ``` One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes. Import attributes are now reported in the [metafile](https://esbuild.github.io/api/#metafile) and are now provided to [on-load plugins](https://esbuild.github.io/plugins/#on-load) as a map in the `with` property. For example, here's an esbuild plugin that turns all imports with a `type` import attribute equal to `'cheese'` into a module that exports the cheese emoji: ```js const cheesePlugin = { name: 'cheese', setup(build) { build.onLoad({ filter: /.*/ }, args => { if (args.with.type === 'cheese') return { contents: `export default "🧀"`, } }) } } require('esbuild').build({ bundle: true, write: false, stdin: { contents: ` import foo from 'data:text/javascript,' with { type: 'cheese' } console.log(foo) `, }, plugins: [cheesePlugin], }).then(result => { const code = new Function(result.outputFiles[0].text) code() }) ``` Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future. - Adjust TypeScript experimental decorator behavior ([#3230](https://togithub.com/evanw/esbuild/issues/3230), [#3326](https://togithub.com/evanw/esbuild/issues/3326), [#3394](https://togithub.com/evanw/esbuild/issues/3394)) With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and `#private` class names. For example: ```js const check = (a: T, b: T): PropertyDecorator => () => console.log(a === b) async function test() { class Foo { static #foo = 1 static bar = 1 + Foo.#foo @check(Foo.#foo, 1) a: any @check(Foo.bar, await Promise.resolve(2)) b: any } } test().then(() => console.log('pass')) ``` This will now print `true true pass` when compiled by esbuild. Previously esbuild evaluated TypeScript decorators outside of the class body, so it didn't allow decorators to access `Foo` or `#foo`. Now esbuild does something different, although it's hard to concisely explain exactly what esbuild is doing now (see the background section below for more information). Note that TypeScript's experimental decorator support is currently buggy: TypeScript's compiler passes this test if only the first `@check` is present or if only the second `@check` is present, but TypeScript's compiler fails this test if both checks are present together. I haven't changed esbuild to match TypeScript's behavior exactly here because I'm waiting for TypeScript to fix these bugs instead. Some background: TypeScript experimental decorators don't have consistent semantics regarding the context that the decorators are evaluated in. For example, TypeScript will let you use `await` within a decorator, which implies that the decorator runs outside the class body (since `await` isn't supported inside a class body), but TypeScript will also let you use `#private` names, which implies that the decorator runs inside the class body (since `#private` names are only supported inside a class body). The value of `this` in a decorator is also buggy (the run-time value of `this` changes if any decorator in the class uses a `#private` name but the type of `this` doesn't change, leading to the type checker no longer matching reality). These inconsistent semantics make it hard for esbuild to implement this feature as decorator evaluation happens in some superposition of both inside and outside the class body that is particular to the internal implementation details of the TypeScript compiler. - Forbid `--keep-names` when targeting old browsers ([#3477](https://togithub.com/evanw/esbuild/issues/3477)) The `--keep-names` setting needs to be able to assign to the `name` property on functions and classes. However, before ES6 this property was non-configurable, and attempting to assign to it would throw an error. So with this release, esbuild will no longer allow you to enable this setting while also targeting a really old browser. ### [`v0.19.6`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0196) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.5...v0.19.6) - Fix a constant folding bug with bigint equality This release fixes a bug where esbuild incorrectly checked for bigint equality by checking the equality of the bigint literal text. This is correct if the bigint doesn't have a radix because bigint literals without a radix are always in canonical form (since leading zeros are not allowed). However, this is incorrect if the bigint has a radix (e.g. `0x123n`) because the canonical form is not enforced when a radix is present. ```js // Original code console.log(!!0n, !!1n, 123n === 123n) console.log(!!0x0n, !!0x1n, 123n === 0x7Bn) // Old output console.log(false, true, true); console.log(true, true, false); // New output console.log(false, true, true); console.log(!!0x0n, !!0x1n, 123n === 0x7Bn); ``` - Add some improvements to the JavaScript minifier This release adds more cases to the JavaScript minifier, including support for inlining `String.fromCharCode` and `String.prototype.charCodeAt` when possible: ```js // Original code document.onkeydown = e => e.keyCode === 'A'.charCodeAt(0) && console.log(String.fromCharCode(55358, 56768)) // Old output (with --minify) document.onkeydown=o=>o.keyCode==="A".charCodeAt(0)&&console.log(String.fromCharCode(55358,56768)); // New output (with --minify) document.onkeydown=o=>o.keyCode===65&&console.log("🧀"); ``` In addition, immediately-invoked function expressions (IIFEs) that return a single expression are now inlined when minifying. This makes it possible to use IIFEs in combination with `@__PURE__` annotations to annotate arbitrary expressions as side-effect free without the IIFE wrapper impacting code size. For example: ```js // Original code const sideEffectFreeOffset = /* @__PURE__ */ (() => computeSomething())() use(sideEffectFreeOffset) // Old output (with --minify) const e=(()=>computeSomething())();use(e); // New output (with --minify) const e=computeSomething();use(e); ``` - Automatically prefix the `mask-composite` CSS property for WebKit ([#3493](https://togithub.com/evanw/esbuild/issues/3493)) The `mask-composite` property will now be prefixed as `-webkit-mask-composite` for older WebKit-based browsers. In addition to prefixing the property name, handling older browsers also requires rewriting the values since WebKit uses non-standard names for the mask composite modes: ```css /* Original code */ div { mask-composite: add, subtract, intersect, exclude; } /* New output (with --target=chrome100) */ div { -webkit-mask-composite: source-over, source-out, source-in, xor; mask-composite: add, subtract, intersect, exclude; } ``` - Avoid referencing `this` from JSX elements in derived class constructors ([#3454](https://togithub.com/evanw/esbuild/issues/3454)) When you enable `--jsx=automatic` and `--jsx-dev`, the JSX transform is supposed to insert `this` as the last argument to the `jsxDEV` function. I'm not sure exactly why this is and I can't find any specification for it, but in any case this causes the generated code to crash when you use a JSX element in a derived class constructor before the call to `super()` as `this` is not allowed to be accessed at that point. For example ```js // Original code class ChildComponent extends ParentComponent { constructor() { super(

) } } // Problematic output (with --loader=jsx --jsx=automatic --jsx-dev) import { jsxDEV } from "react/jsx-dev-runtime"; class ChildComponent extends ParentComponent { constructor() { super(/* @__PURE__ */ jsxDEV("div", {}, void 0, false, { fileName: "", lineNumber: 3, columnNumber: 15 }, this)); // The reference to "this" crashes here } } ``` The TypeScript compiler doesn't handle this at all while the Babel compiler just omits `this` for the entire constructor (even after the call to `super()`). There seems to be no specification so I can't be sure that this change doesn't break anything important. But given that Babel is pretty loose with this and TypeScript doesn't handle this at all, I'm guessing this value isn't too important. React's blog post seems to indicate that this value was intended to be used for a React-specific migration warning at some point, so it could even be that this value is irrelevant now. Anyway the crash in this case should now be fixed. - Allow package subpath imports to map to node built-ins ([#3485](https://togithub.com/evanw/esbuild/issues/3485)) You are now able to use a [subpath import](https://nodejs.org/api/packages.html#subpath-imports) in your package to resolve to a node built-in module. For example, with a `package.json` file like this: ```json { "type": "module", "imports": { "#stream": { "node": "stream", "default": "./stub.js" } } } ``` You can now import from node's `stream` module like this: ```js import * as stream from '#stream'; console.log(Object.keys(stream)); ``` This will import from node's `stream` module when the platform is `node` and from `./stub.js` otherwise. - No longer throw an error when a `Symbol` is missing ([#3453](https://togithub.com/evanw/esbuild/issues/3453)) Certain JavaScript syntax features use special properties on the global `Symbol` object. For example, the asynchronous iteration syntax uses `Symbol.asyncIterator`. Previously esbuild's generated code for older browsers required this symbol to be polyfilled. However, starting with this release esbuild will use [`Symbol.for()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/for) to construct these symbols if they are missing instead of throwing an error about a missing polyfill. This means your code no longer needs to include a polyfill for missing symbols as long as your code also uses `Symbol.for()` for missing symbols. - Parse upcoming changes to TypeScript syntax ([#3490](https://togithub.com/evanw/esbuild/issues/3490), [#3491](https://togithub.com/evanw/esbuild/pull/3491)) With this release, you can now use `from` as the name of a default type-only import in TypeScript code, as well as `of` as the name of an `await using` loop iteration variable: ```ts import type from from 'from' for (await using of of of) ; ``` This matches similar changes in the TypeScript compiler ([#56376](https://togithub.com/microsoft/TypeScript/issues/56376) and [#55555](https://togithub.com/microsoft/TypeScript/issues/55555)) which will start allowing this syntax in an upcoming version of TypeScript. Please never actually write code like this. The type-only import syntax change was contributed by [@magic-akari](https://togithub.com/magic-akari).

nuxt/nuxt (nuxt)

### [`v3.8.2`](https://togithub.com/nuxt/nuxt/compare/v3.8.1...v3.8.2) [Compare Source](https://togithub.com/nuxt/nuxt/compare/v3.8.1...v3.8.2)

stormwarning/stylelint-config-recess-order (stylelint-config-recess-order)

### [`v4.4.0`](https://togithub.com/stormwarning/stylelint-config-recess-order/blob/HEAD/CHANGELOG.md#440--2023-11-19) [Compare Source](https://togithub.com/stormwarning/stylelint-config-recess-order/compare/v4.3.0...v4.4.0) ##### Minor Changes - Add Masking properties [#349](https://togithub.com/stormwarning/stylelint-config-recess-order/pull/349) - [`mask-border`](https://developer.mozilla.org/en-US/docs/Web/CSS/mask-border) and related longhand properties - [`mask`](https://developer.mozilla.org/en-US/docs/Web/CSS/mask) and related longhand properties `mask` was previously included within some SVG-specific properties — it’s been moved above those and below border & outline properties. `mask-border` properties are sorted above `mask` to highlight the fact that `mask` will reset `mask-border` to its initial value ([as per W3C spec](https://drafts.fxtf.org/css-masking/#the-mask)). I’m not familiar with this properties; if this order is problematic in practice, please file an issue! ##### Patch Changes - Fix `block-size` property support [#346](https://togithub.com/stormwarning/stylelint-config-recess-order/pull/346)\ Thanks [@azat-io](https://togithub.com/azat-io)!

vuejs/vitepress (vitepress)

### [`v1.0.0-rc.29`](https://togithub.com/vuejs/vitepress/blob/HEAD/CHANGELOG.md#100-rc29-2023-11-19) [Compare Source](https://togithub.com/vuejs/vitepress/compare/v1.0.0-rc.28...v1.0.0-rc.29) ##### Bug Fixes - **client:** regression - router not working without .html present ([d63cb86](https://togithub.com/vuejs/vitepress/commit/d63cb867b14ba49c8333ad0d69d33874e2ece6c6)), closes [#3225](https://togithub.com/vuejs/vitepress/issues/3225)

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.

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

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

basics / nuxt-booster

chore(deps): update all non-major dependencies #903

Release Notes

Configuration