typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v7.12.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#7120-2024-06-03)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v7.11.0...v7.12.0)
##### 🚀 Features
- **eslint-plugin:** \[no-useless-template-literals] rename to `no-useless-template-expression` (deprecate `no-useless-template-literals`)
- **rule-tester:** check for parsing errors in suggestion fixes
- **rule-tester:** port `checkDuplicateTestCases` from ESLint
- **eslint-plugin:** \[no-floating-promises] add option 'allowForKnownSafePromises'
##### 🩹 Fixes
- no-useless-template-expression -> no-unnecessary-template-expression
- **eslint-plugin:** \[no-unnecessary-type-assertion] combine template literal check with `const` variable check
- **eslint-plugin:** \[dot-notation] fix false positive when accessing private/protected property with optional chaining
- **eslint-plugin:** \[explicit-member-accessibility] refine report locations
- **eslint-plugin:** \[no-unnecessary-type-assertion] declares are always defined, so always check `declare`s
- **eslint-plugin:** \[prefer-literal-enum-member] allow using member it self on allowBitwiseExpressions
- **eslint-plugin:** \[return-await] clean up in-try-catch detection and make autofixes safe
- **eslint-plugin:** \[member-ordering] also TSMethodSignature can be get/set
##### ❤️ Thank You
- Abraham Guo
- Han Yeong-woo
- Joshua Chen
- Kim Sang Du
- Kirk Waiblinger
- YeonJuan
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v7.12.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#7120-2024-06-03)
[Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v7.11.0...v7.12.0)
##### 🩹 Fixes
- **types:** correct typing ParserOptions
##### ❤️ Thank You
- Abraham Guo
- Han Yeong-woo
- Joshua Chen
- Kim Sang Du
- Kirk Waiblinger
- YeonJuan
You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.
vercel/vercel (@vercel/build-utils)
### [`v8.2.2`](https://togithub.com/vercel/vercel/releases/tag/%40vercel/build-utils%408.2.2)
[Compare Source](https://togithub.com/vercel/vercel/compare/@vercel/build-utils@8.2.1...@vercel/build-utils@8.2.2)
##### Patch Changes
- Change node 16.x EOL for Vercel ([#11704](https://togithub.com/vercel/vercel/pull/11704))
- Improve error message and refactor ([#11706](https://togithub.com/vercel/vercel/pull/11706))
- \[built-utils] Handle case of not having lockfile when corepack is enabled ([#11697](https://togithub.com/vercel/vercel/pull/11697))
vercel/nft (@vercel/nft)
### [`v0.27.2`](https://togithub.com/vercel/nft/releases/tag/0.27.2)
[Compare Source](https://togithub.com/vercel/nft/compare/0.27.1...0.27.2)
##### Bug Fixes
- Support browser overrides in package.json ([#424](https://togithub.com/vercel/nft/issues/424)) ([ff4341b](https://togithub.com/vercel/nft/commit/ff4341b9c65158bcd2d301f0281cf55d503c3b2b))
vercel/vercel (@vercel/node)
### [`v3.1.7`](https://togithub.com/vercel/vercel/blob/HEAD/packages/node/CHANGELOG.md#317)
[Compare Source](https://togithub.com/vercel/vercel/compare/@vercel/node@3.1.6...@vercel/node@3.1.7)
##### Patch Changes
- Upgrade to [@vercel/nft](https://togithub.com/vercel/nft) 0.27.2 with browser remapping support ([#11700](https://togithub.com/vercel/vercel/pull/11700))
- Updated dependencies \[[`5c12ed695`](https://togithub.com/vercel/vercel/commit/5c12ed69500ceff6a9dc544eab0acd7af64c044a), [`21444a38e`](https://togithub.com/vercel/vercel/commit/21444a38e50ed680c91b0e3955f15e378eeda64b), [`06d2d860e`](https://togithub.com/vercel/vercel/commit/06d2d860e47aed792247bf929805b180ed6e2dab)]:
- [@vercel/build-utils](https://togithub.com/vercel/build-utils)[@8](https://togithub.com/8).2.2
evanw/esbuild (esbuild)
### [`v0.21.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0215)
[Compare Source](https://togithub.com/evanw/esbuild/compare/v0.21.4...v0.21.5)
- Fix `Symbol.metadata` on classes without a class decorator ([#3781](https://togithub.com/evanw/esbuild/issues/3781))
This release fixes a bug with esbuild's support for the [decorator metadata proposal](https://togithub.com/tc39/proposal-decorator-metadata). Previously esbuild only added the `Symbol.metadata` property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the `Symbol.metadata` property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.
- Allow unknown import attributes to be used with the `copy` loader ([#3792](https://togithub.com/evanw/esbuild/issues/3792))
Import attributes (the `with` keyword on `import` statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load `./bagel.js` as type `bagel`:
```js
// This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }
```
Because of that, bundling this code with esbuild is an error unless the file `./bagel.js` is external to the bundle (such as with `--bundle --external:./bagel.js`).
However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the `copy` loader. That's because the `copy` loader behaves similarly to `--external` in that the file is left external to the bundle. The difference is that the `copy` loader copies the file into the output folder and rewrites the import path while `--external` doesn't. That means the following will now work with the `copy` loader (such as with `--bundle --loader:.bagel=copy`):
```js
// This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }
```
- Support import attributes with glob-style imports ([#3797](https://togithub.com/evanw/esbuild/issues/3797))
This release adds support for import attributes (the `with` option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:
```ts
async function loadLocale(locale: string): Locale {
const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
return unpackLocale(locale, data)
}
```
Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:
✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data
example.ts:2:28:
2 │ const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition, this change means plugins can now access the contents of `with` for glob-style imports.
- Support `${configDir}` in `tsconfig.json` files ([#3782](https://togithub.com/evanw/esbuild/issues/3782))
This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence `${configDir}` is now respected at the start of `baseUrl` and `paths` values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base `tsconfig.json` files specified via `extends` refer to the directory of the top-level `tsconfig.json` file. Here is an example:
```json
{
"compilerOptions": {
"paths": {
"js/*": ["${configDir}/dist/js/*"]
}
}
}
```
You can read more in [TypeScript's blog post about their upcoming 5.5 release](https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/#the-configdir-template-variable-for-configuration-files). Note that this feature does not make use of template literals (you need to use `"${configDir}/dist/js/*"` not `` `${configDir}/dist/js/*` ``). The syntax for `tsconfig.json` is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes `${configDir}` in strings for certain path-like properties, and only at the beginning of the string.
- Fix internal error with `--supported:object-accessors=false` ([#3794](https://togithub.com/evanw/esbuild/issues/3794))
This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with `--supported:object-accessors=false`. The reason is that esbuild introduced code that does `{ get [name]() {} }` which uses both the `object-extensions` feature for the `[name]` and the `object-accessors` feature for the `get`, but esbuild was incorrectly only checking for `object-extensions` and not for `object-accessors`. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add `--supported:object-extensions=false`.
prettier/prettier (prettier)
### [`v3.3.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#331)
[Compare Source](https://togithub.com/prettier/prettier/compare/3.3.0...3.3.1)
[diff](https://togithub.com/prettier/prettier/compare/3.3.0...3.3.1)
##### Preserve empty lines in front matter ([#16347](https://togithub.com/prettier/prettier/pull/16347) by [@fisker](https://togithub.com/fisker))
```markdown
---
foo:
- bar1
- bar2
- bar3
---
Markdown
---
foo:
- bar1
- bar2
- bar3
---
Markdown
---
foo:
- bar1
- bar2
- bar3
---
Markdown
```
##### Preserve explicit language in front matter ([#16348](https://togithub.com/prettier/prettier/pull/16348) by [@fisker](https://togithub.com/fisker))
```markdown
---yaml
title: Hello
slug: home
---
---
title: Hello
slug: home
---
---yaml
title: Hello
slug: home
---
```
##### Avoid line breaks in import attributes ([#16349](https://togithub.com/prettier/prettier/pull/16349) by [@fisker](https://togithub.com/fisker))
```jsx
// Input
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };
// Prettier 3.3.0
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type:
"json" };
// Prettier 3.3.1
import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" };
```
vikejs/vike (vike)
### [`v0.4.174`](https://togithub.com/vikejs/vike/blob/HEAD/CHANGELOG.md#04174-2024-06-06)
[Compare Source](https://togithub.com/vikejs/vike/compare/v0.4.173...v0.4.174)
##### Bug Fixes
- declare semver dependency (fix [#1676](https://togithub.com/vikejs/vike/issues/1676)) ([8f0b499](https://togithub.com/vikejs/vike/commit/8f0b49997f9ccdb5f1f9802b99e723c2bf0f8cce))
### [`v0.4.173`](https://togithub.com/vikejs/vike/blob/HEAD/CHANGELOG.md#04173-2024-06-05)
[Compare Source](https://togithub.com/vikejs/vike/compare/v0.4.172...v0.4.173)
##### Bug Fixes
- `export type { ImportString }` ([1161acd](https://togithub.com/vikejs/vike/commit/1161acd6f45d26a037631c238945b01dd1740667))
- add vite.config.js headers to SSR response ([#1669](https://togithub.com/vikejs/vike/issues/1669)) ([605b4a5](https://togithub.com/vikejs/vike/commit/605b4a502fc5e34ea8948216ddee607e9a558666))
- always show assert stack traces upon DEBUG=vike:error ([a437fe9](https://togithub.com/vikejs/vike/commit/a437fe9b67375cb124889eeee7e28db438caa854))
- enforce Vike extension conventions ([be770f2](https://togithub.com/vikejs/vike/commit/be770f2edcecf051c0556e0774e7b77b614b529f))
- fix deducing of extension name ([2c361cc](https://togithub.com/vikejs/vike/commit/2c361cc87228304af728164cc3615bd0900b7e9e))
- move dev code outside of prod runtime ([5d69efa](https://togithub.com/vikejs/vike/commit/5d69efa41688c1608fff215646b8641bc6a99b66))
- prettify logged URL ([#1658](https://togithub.com/vikejs/vike/issues/1658)) ([ea2b76c](https://togithub.com/vikejs/vike/commit/ea2b76c5fd96298f7b5b750c78a4993f11e1b2c2))
- remove ImportString from pageContext.config type ([1b7b761](https://togithub.com/vikejs/vike/commit/1b7b7613f9364e617341f5285b27646a72592edf))
- remove outdated Bun workaround ([6701c7b](https://togithub.com/vikejs/vike/commit/6701c7b4bfeb0fd23cccc6bd870ff4ade72c2267))
- remove too strict convention ([7b30d71](https://togithub.com/vikejs/vike/commit/7b30d7197dbee6545e4b0db65744d619f34c569c))
- support pre-releases for require setting ([24e2d90](https://togithub.com/vikejs/vike/commit/24e2d909ab49f128711e96de31d544a574a74c71))
- support UTF-9 file paths (fix [#1658](https://togithub.com/vikejs/vike/issues/1658)) ([a7cc8ad](https://togithub.com/vikejs/vike/commit/a7cc8adb3f8ccdf2718ad334280d232b3c6069a5))
##### Features
- \[experimental] new setting crawl.git (closes [#1655](https://togithub.com/vikejs/vike/issues/1655)) ([c1b0884](https://togithub.com/vikejs/vike/commit/c1b08840bd2a0d741bffc78a045edbc77fbf64f4))
- new setting `clientHooks` (closes [#1671](https://togithub.com/vikejs/vike/issues/1671)) ([c1dcd5f](https://togithub.com/vikejs/vike/commit/c1dcd5f3c01eee8cb888912f0860d30b87f71521))
- new setting `require` for Vike extensions (fix [#1668](https://togithub.com/vikejs/vike/issues/1668)) ([5ceeb1a](https://togithub.com/vikejs/vike/commit/5ceeb1ac0affae3de47bf4d881f477dccea62a94))
vitejs/vite (vite)
### [`v5.2.13`](https://togithub.com/vitejs/vite/releases/tag/v5.2.13)
[Compare Source](https://togithub.com/vitejs/vite/compare/v5.2.12...v5.2.13)
Please refer to [CHANGELOG.md](https://togithub.com/vitejs/vite/blob/v5.2.13/packages/vite/CHANGELOG.md) for details.
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.
This PR contains the following updates:
^7.11.0
->^7.12.0
^7.11.0
->^7.12.0
^8.2.1
->^8.2.2
^0.27.1
->^0.27.2
^3.1.6
->^3.1.7
^0.21.4
->^0.21.5
^3.3.0
->^3.3.1
^0.4.172
->^0.4.174
^5.2.12
->^5.2.13
Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
### [`v7.12.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#7120-2024-06-03) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v7.11.0...v7.12.0) ##### 🚀 Features - **eslint-plugin:** \[no-useless-template-literals] rename to `no-useless-template-expression` (deprecate `no-useless-template-literals`) - **rule-tester:** check for parsing errors in suggestion fixes - **rule-tester:** port `checkDuplicateTestCases` from ESLint - **eslint-plugin:** \[no-floating-promises] add option 'allowForKnownSafePromises' ##### 🩹 Fixes - no-useless-template-expression -> no-unnecessary-template-expression - **eslint-plugin:** \[no-unnecessary-type-assertion] combine template literal check with `const` variable check - **eslint-plugin:** \[dot-notation] fix false positive when accessing private/protected property with optional chaining - **eslint-plugin:** \[explicit-member-accessibility] refine report locations - **eslint-plugin:** \[no-unnecessary-type-assertion] declares are always defined, so always check `declare`s - **eslint-plugin:** \[prefer-literal-enum-member] allow using member it self on allowBitwiseExpressions - **eslint-plugin:** \[return-await] clean up in-try-catch detection and make autofixes safe - **eslint-plugin:** \[member-ordering] also TSMethodSignature can be get/set ##### ❤️ Thank You - Abraham Guo - Han Yeong-woo - Joshua Chen - Kim Sang Du - Kirk Waiblinger - YeonJuan You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v7.12.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#7120-2024-06-03) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v7.11.0...v7.12.0) ##### 🩹 Fixes - **types:** correct typing ParserOptions ##### ❤️ Thank You - Abraham Guo - Han Yeong-woo - Joshua Chen - Kim Sang Du - Kirk Waiblinger - YeonJuan You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.vercel/vercel (@vercel/build-utils)
### [`v8.2.2`](https://togithub.com/vercel/vercel/releases/tag/%40vercel/build-utils%408.2.2) [Compare Source](https://togithub.com/vercel/vercel/compare/@vercel/build-utils@8.2.1...@vercel/build-utils@8.2.2) ##### Patch Changes - Change node 16.x EOL for Vercel ([#11704](https://togithub.com/vercel/vercel/pull/11704)) - Improve error message and refactor ([#11706](https://togithub.com/vercel/vercel/pull/11706)) - \[built-utils] Handle case of not having lockfile when corepack is enabled ([#11697](https://togithub.com/vercel/vercel/pull/11697))vercel/nft (@vercel/nft)
### [`v0.27.2`](https://togithub.com/vercel/nft/releases/tag/0.27.2) [Compare Source](https://togithub.com/vercel/nft/compare/0.27.1...0.27.2) ##### Bug Fixes - Support browser overrides in package.json ([#424](https://togithub.com/vercel/nft/issues/424)) ([ff4341b](https://togithub.com/vercel/nft/commit/ff4341b9c65158bcd2d301f0281cf55d503c3b2b))vercel/vercel (@vercel/node)
### [`v3.1.7`](https://togithub.com/vercel/vercel/blob/HEAD/packages/node/CHANGELOG.md#317) [Compare Source](https://togithub.com/vercel/vercel/compare/@vercel/node@3.1.6...@vercel/node@3.1.7) ##### Patch Changes - Upgrade to [@vercel/nft](https://togithub.com/vercel/nft) 0.27.2 with browser remapping support ([#11700](https://togithub.com/vercel/vercel/pull/11700)) - Updated dependencies \[[`5c12ed695`](https://togithub.com/vercel/vercel/commit/5c12ed69500ceff6a9dc544eab0acd7af64c044a), [`21444a38e`](https://togithub.com/vercel/vercel/commit/21444a38e50ed680c91b0e3955f15e378eeda64b), [`06d2d860e`](https://togithub.com/vercel/vercel/commit/06d2d860e47aed792247bf929805b180ed6e2dab)]: - [@vercel/build-utils](https://togithub.com/vercel/build-utils)[@8](https://togithub.com/8).2.2evanw/esbuild (esbuild)
### [`v0.21.5`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0215) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.21.4...v0.21.5) - Fix `Symbol.metadata` on classes without a class decorator ([#3781](https://togithub.com/evanw/esbuild/issues/3781)) This release fixes a bug with esbuild's support for the [decorator metadata proposal](https://togithub.com/tc39/proposal-decorator-metadata). Previously esbuild only added the `Symbol.metadata` property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the `Symbol.metadata` property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself. - Allow unknown import attributes to be used with the `copy` loader ([#3792](https://togithub.com/evanw/esbuild/issues/3792)) Import attributes (the `with` keyword on `import` statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load `./bagel.js` as type `bagel`: ```js // This is an error with "--bundle" without also using "--external:./bagel.js" import tasty from "./bagel.js" with { type: "bagel" } ``` Because of that, bundling this code with esbuild is an error unless the file `./bagel.js` is external to the bundle (such as with `--bundle --external:./bagel.js`). However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the `copy` loader. That's because the `copy` loader behaves similarly to `--external` in that the file is left external to the bundle. The difference is that the `copy` loader copies the file into the output folder and rewrites the import path while `--external` doesn't. That means the following will now work with the `copy` loader (such as with `--bundle --loader:.bagel=copy`): ```js // This is no longer an error with "--bundle" and "--loader:.bagel=copy" import tasty from "./tasty.bagel" with { type: "bagel" } ``` - Support import attributes with glob-style imports ([#3797](https://togithub.com/evanw/esbuild/issues/3797)) This release adds support for import attributes (the `with` option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly: ```ts async function loadLocale(locale: string): Locale { const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } }) return unpackLocale(locale, data) } ``` Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error: ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data example.ts:2:28: 2 │ const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } }) ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~ In addition, this change means plugins can now access the contents of `with` for glob-style imports. - Support `${configDir}` in `tsconfig.json` files ([#3782](https://togithub.com/evanw/esbuild/issues/3782)) This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence `${configDir}` is now respected at the start of `baseUrl` and `paths` values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base `tsconfig.json` files specified via `extends` refer to the directory of the top-level `tsconfig.json` file. Here is an example: ```json { "compilerOptions": { "paths": { "js/*": ["${configDir}/dist/js/*"] } } } ``` You can read more in [TypeScript's blog post about their upcoming 5.5 release](https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/#the-configdir-template-variable-for-configuration-files). Note that this feature does not make use of template literals (you need to use `"${configDir}/dist/js/*"` not `` `${configDir}/dist/js/*` ``). The syntax for `tsconfig.json` is still just JSON with comments, and JSON syntax does not allow template literals. This feature only recognizes `${configDir}` in strings for certain path-like properties, and only at the beginning of the string. - Fix internal error with `--supported:object-accessors=false` ([#3794](https://togithub.com/evanw/esbuild/issues/3794)) This release fixes a regression in 0.21.0 where some code that was added to esbuild's internal runtime library of helper functions for JavaScript decorators fails to parse when you configure esbuild with `--supported:object-accessors=false`. The reason is that esbuild introduced code that does `{ get [name]() {} }` which uses both the `object-extensions` feature for the `[name]` and the `object-accessors` feature for the `get`, but esbuild was incorrectly only checking for `object-extensions` and not for `object-accessors`. Additional tests have been added to avoid this type of issue in the future. A workaround for this issue in earlier releases is to also add `--supported:object-extensions=false`.prettier/prettier (prettier)
### [`v3.3.1`](https://togithub.com/prettier/prettier/blob/HEAD/CHANGELOG.md#331) [Compare Source](https://togithub.com/prettier/prettier/compare/3.3.0...3.3.1) [diff](https://togithub.com/prettier/prettier/compare/3.3.0...3.3.1) ##### Preserve empty lines in front matter ([#16347](https://togithub.com/prettier/prettier/pull/16347) by [@fisker](https://togithub.com/fisker)) ```markdown --- foo: - bar1 - bar2 - bar3 --- Markdown --- foo: - bar1 - bar2 - bar3 --- Markdown --- foo: - bar1 - bar2 - bar3 --- Markdown ``` ##### Preserve explicit language in front matter ([#16348](https://togithub.com/prettier/prettier/pull/16348) by [@fisker](https://togithub.com/fisker)) ```markdown ---yaml title: Hello slug: home --- --- title: Hello slug: home --- ---yaml title: Hello slug: home --- ``` ##### Avoid line breaks in import attributes ([#16349](https://togithub.com/prettier/prettier/pull/16349) by [@fisker](https://togithub.com/fisker)) ```jsx // Input import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" }; // Prettier 3.3.0 import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" }; // Prettier 3.3.1 import something from "./some-very-very-very-very-very-very-very-very-long-path.json" with { type: "json" }; ```vikejs/vike (vike)
### [`v0.4.174`](https://togithub.com/vikejs/vike/blob/HEAD/CHANGELOG.md#04174-2024-06-06) [Compare Source](https://togithub.com/vikejs/vike/compare/v0.4.173...v0.4.174) ##### Bug Fixes - declare semver dependency (fix [#1676](https://togithub.com/vikejs/vike/issues/1676)) ([8f0b499](https://togithub.com/vikejs/vike/commit/8f0b49997f9ccdb5f1f9802b99e723c2bf0f8cce)) ### [`v0.4.173`](https://togithub.com/vikejs/vike/blob/HEAD/CHANGELOG.md#04173-2024-06-05) [Compare Source](https://togithub.com/vikejs/vike/compare/v0.4.172...v0.4.173) ##### Bug Fixes - `export type { ImportString }` ([1161acd](https://togithub.com/vikejs/vike/commit/1161acd6f45d26a037631c238945b01dd1740667)) - add vite.config.js headers to SSR response ([#1669](https://togithub.com/vikejs/vike/issues/1669)) ([605b4a5](https://togithub.com/vikejs/vike/commit/605b4a502fc5e34ea8948216ddee607e9a558666)) - always show assert stack traces upon DEBUG=vike:error ([a437fe9](https://togithub.com/vikejs/vike/commit/a437fe9b67375cb124889eeee7e28db438caa854)) - enforce Vike extension conventions ([be770f2](https://togithub.com/vikejs/vike/commit/be770f2edcecf051c0556e0774e7b77b614b529f)) - fix deducing of extension name ([2c361cc](https://togithub.com/vikejs/vike/commit/2c361cc87228304af728164cc3615bd0900b7e9e)) - move dev code outside of prod runtime ([5d69efa](https://togithub.com/vikejs/vike/commit/5d69efa41688c1608fff215646b8641bc6a99b66)) - prettify logged URL ([#1658](https://togithub.com/vikejs/vike/issues/1658)) ([ea2b76c](https://togithub.com/vikejs/vike/commit/ea2b76c5fd96298f7b5b750c78a4993f11e1b2c2)) - remove ImportString from pageContext.config type ([1b7b761](https://togithub.com/vikejs/vike/commit/1b7b7613f9364e617341f5285b27646a72592edf)) - remove outdated Bun workaround ([6701c7b](https://togithub.com/vikejs/vike/commit/6701c7b4bfeb0fd23cccc6bd870ff4ade72c2267)) - remove too strict convention ([7b30d71](https://togithub.com/vikejs/vike/commit/7b30d7197dbee6545e4b0db65744d619f34c569c)) - support pre-releases for require setting ([24e2d90](https://togithub.com/vikejs/vike/commit/24e2d909ab49f128711e96de31d544a574a74c71)) - support UTF-9 file paths (fix [#1658](https://togithub.com/vikejs/vike/issues/1658)) ([a7cc8ad](https://togithub.com/vikejs/vike/commit/a7cc8adb3f8ccdf2718ad334280d232b3c6069a5)) ##### Features - \[experimental] new setting crawl.git (closes [#1655](https://togithub.com/vikejs/vike/issues/1655)) ([c1b0884](https://togithub.com/vikejs/vike/commit/c1b08840bd2a0d741bffc78a045edbc77fbf64f4)) - new setting `clientHooks` (closes [#1671](https://togithub.com/vikejs/vike/issues/1671)) ([c1dcd5f](https://togithub.com/vikejs/vike/commit/c1dcd5f3c01eee8cb888912f0860d30b87f71521)) - new setting `require` for Vike extensions (fix [#1668](https://togithub.com/vikejs/vike/issues/1668)) ([5ceeb1a](https://togithub.com/vikejs/vike/commit/5ceeb1ac0affae3de47bf4d881f477dccea62a94))vitejs/vite (vite)
### [`v5.2.13`](https://togithub.com/vitejs/vite/releases/tag/v5.2.13) [Compare Source](https://togithub.com/vitejs/vite/compare/v5.2.12...v5.2.13) Please refer to [CHANGELOG.md](https://togithub.com/vitejs/vite/blob/v5.2.13/packages/vite/CHANGELOG.md) for details.Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.