chore(deps): update all non-major dependencies (minor) by renovate[bot] · Pull Request #293 · nuxt/nuxt.new

renovate · 2024-11-18T22:02:09Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nuxt/ui (source)	`^2.20.0` -> `^2.21.1`
@nuxtjs/critters	`^0.7.2` -> `^0.8.0`
@playwright/test (source)	`1.48.2` -> `1.51.1`
pnpm (source)	`10.2.1` -> `10.7.0`
typescript (source)	`^5.7.3` -> `^5.8.2`
vue-tsc (source)	`2.1.10` -> `2.2.8`

Release Notes

nuxt/ui (@nuxt/ui)

`v2.21.1`

Compare Source

🚀 Features

Form: add standard schema support (#2880) (9c36d37)
module: add colorMode option (d2ceead), closes #3143
SelectMenu: add inputTargetForm prop to handle input validation (#3107) (feb716c)

🐛 Bug Fixes

Alert/Notification: allow description ui override (125a281), closes #2554
Table: revert #2600 to fix excessive column data slot re-renders (#3375) (23d9b51)

👋 New Contributors

@LeonidevFR made their first contribution in https://github.com/nuxt/ui/pull/3107
@coreyshuman made their first contribution in https://github.com/nuxt/ui/pull/3375

Full Changelog: nuxt/ui@v2.21.0...v2.21.1

`v2.21.0`

Compare Source

🚀 Features

module: handle tailwindMerge config from app.config (#2902) (ea15e21)

🐛 Bug Fixes

Table: v-model causing first column missing (#2890) (d573fb6)
Table: remove @select event on checkbox (#3042) (d9d4f19)
tailwind: use mjs template (#2945) (8cf9f27)

New Contributors

@stijns96 made their first contribution in https://github.com/nuxt/ui/pull/2902

Full Changelog: nuxt/ui@v2.20.0...v2.21.0

nuxt-modules/critters (@nuxtjs/critters)

`v0.8.0`

Compare Source

🐞 Bug Fixes

Use Options from beasties - by @danielroe (29a9b)
Unpin dependencies - by @danielroe (4e6b3)

View changes on GitHub

microsoft/playwright (@playwright/test)

`v1.51.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/35093 - [Regression]: TimeoutOverflowWarning: 2149630.634 does not fit into a 32-bit signed integer
https://github.com/microsoft/playwright/issues/35138 - [Regression]: TypeError: Cannot read properties of undefined (reading 'expectInfo')

Browser Versions

Chromium 134.0.6998.35
Mozilla Firefox 135.0
WebKit 18.4

This version was also tested against the following stable channels:

Google Chrome 133
Microsoft Edge 133

`v1.51.0`

Compare Source

`v1.50.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/34483 - [Feature]: single aria snapshot for different engines/browsershttps://github.com/microsoft/playwright/issues/344977 - [Bug]: Firefox not handling keepalive: true fetch requesthttps://github.com/microsoft/playwright/issues/3450404 - [Bug]: update snapshots not creating good difhttps://github.com/microsoft/playwright/issues/34507507 - [Bug]: snapshotPathTemplate doesnt work when multiple projehttps://github.com/microsoft/playwright/issues/344624462 - [Bug]: updateSnapshots "changed" throws an error

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

`v1.50.0`

Compare Source

Test runner

New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

New method test.step.skip() to disable execution of a test step.

test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.
Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.
Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.
New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.
```
npx playwright test --update-snapshots=changed --update-source-method=3way
```
Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.
Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.
New option pathTemplate for toHaveScreenshot and toMatchAriaSnapshot assertions in the testConfig.expect configuration.

UI updates

Updated default HTML reporter to improve display of attachments.
New button for picking elements to produce aria snapshots.
Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
Call and Network panels now display additional time information.

Breaking

expect(locator).toBeEditable() and locator.isEditable() now throw if the target element is not <input>, <select>, or a number of other editable elements.
Option testConfig.updateSnapshots now updates all snapshots when set to all, rather than only the failed/changed snapshots. Use the new enum changed to keep the old functionality of only updating the changed snapshots.

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

`v1.49.1`

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/33802 - [Bug]: Codegen's Clear button doesn't work if not recordinghttps://github.com/microsoft/playwright/issues/338066 - [Bug]: playwright hangs while waiting for pending navigationhttps://github.com/microsoft/playwright/issues/3378787 - [Bug]: VSC extension isn't capturing all entered tehttps://github.com/microsoft/playwright/issues/33788788 - [Regression]: Double clicking the steps in trace viewer doesn't filter actihttps://github.com/microsoft/playwright/issues/337723772 - [Bug]: aria_snapshot generates invalid yaml when combined with an aria-label attrhttps://github.com/microsoft/playwright/issues/3379133791 - [Bug]: text input with number value raises "container is not iterable" with to_match_aria_snahttps://github.com/microsoft/playwright/issues/33644/33644 - [Bug]: getByRole can't find element with the accessible name from label element when aria-labelledby is nothttps://github.com/microsoft/playwright/issues/33660s/33660 - [Regression]: Unable to open Playwright UI in Dark Mode

Browser Versions

Chromium 131.0.6778.33
Mozilla Firefox 132.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 130
Microsoft Edge 130

`v1.49.0`

Compare Source

Aria snapshots

New assertion expect(locator).toMatchAriaSnapshot() verifies page structure by comparing to an expected accessibility tree, represented as YAML.

await page.goto('https://playwright.dev');
await expect(page.locator('body')).toMatchAriaSnapshot(`
  - banner:
    - heading /Playwright enables reliable/ [level=1]
    - link "Get started"
    - link "Star microsoft/playwright on GitHub"
  - main:
    - img "Browsers (Chromium, Firefox, WebKit)"
    - heading "Any browser • Any platform • One API"
`);

You can generate this assertion with Test Generator and update the expected snapshot with --update-snapshots command line flag.

Learn more in the aria snapshots guide.

Test runner

New option testConfig.tsconfig allows to specify a single tsconfig to be used for all tests.
New method test.fail.only() to focus on a failing test.
Options testConfig.globalSetup and testConfig.globalTeardown now support multiple setups/teardowns.
New value 'on-first-failure' for testOptions.screenshot.
Added "previous" and "next" buttons to the HTML report to quickly switch between test cases.
New properties testInfoError.cause and testError.cause mirroring Error.cause.

Breaking: channels `chrome`, `msedge` and similar switch to new headless

This change affects you if you're using one of the following channels in your playwright.config.ts:

chrome, chrome-dev, chrome-beta, or chrome-canary
msedge, msedge-dev, msedge-beta, or msedge-canary

What do I need to do?

After updating to Playwright v1.49, run your test suite. If it still passes, you're good to go. If not, you will probably need to update your snapshots, and adapt some of your test code around PDF viewers and extensions. See issue #33566 for more details.

Other breaking changes

There will be no more updates for WebKit on Ubuntu 20.04 and Debian 11. We recommend updating your OS to a later version.
Package @playwright/experimental-ct-vue2 will no longer be updated.
Package @playwright/experimental-ct-solid will no longer be updated.

Try new Chromium headless

You can opt into the new headless mode by using 'chromium' channel. As official Chrome documentation puts it:

New Headless on the other hand is the real Chrome browser, and is thus more authentic, reliable, and offers more features. This makes it more suitable for high-accuracy end-to-end web app testing or browser extension testing.

See issue #33566 for the list of possible breakages you could encounter and more details on Chromium headless. Please file an issue if you see any problems after opting in.

import { defineConfig, devices } from '@&#8203;playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'chromium',
      use: { ...devices['Desktop Chrome'], channel: 'chromium' },
    },
  ],
});

Miscellaneous

<canvas> elements inside a snapshot now draw a preview.
New method tracing.group() to visually group actions in the trace.
Playwright docker images switched from Node.js v20 to Node.js v22 LTS.

Browser Versions

Chromium 131.0.6778.33
Mozilla Firefox 132.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 130
Microsoft Edge 130

pnpm/pnpm (pnpm)

`v10.7.0`

Compare Source

Minor Changes

pnpm config get and list also show settings set in pnpm-workspace.yaml files #9316.
It should be possible to use env variables in pnpm-workspace.yaml setting names and value.
Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range * is the same as name-only, except that patch application failure will not be ignored.

For example:
```
patchedDependencies:
  foo: patches/foo-1.patch
  foo@^2.0.0: patches/foo-2.patch
  foo@2.1.0: patches/foo-3.patch
```
The above configuration would apply patches/foo-3.patch to foo@2.1.0, patches/foo-2.patch to all foo versions which satisfy ^2.0.0 except 2.1.0, and patches/foo-1.patch to the remaining foo versions.
[!WARNING]
The version ranges should not overlap. If you want to specialize a sub range, make sure to exclude it from the other keys. For example:
```
# pnpm-workspace.yaml
patchedDependencies:
  # the specialized sub range
  'foo@2.2.0-2.8.0': patches/foo.2.2.0-2.8.0.patch
  # the more general patch, excluding the sub range above
  'foo@>=2.0.0 <2.2.0 || >2.8.0': 'patches/foo.gte2.patch
```
In most cases, however, it's sufficient to just define an exact version to override the range.
pnpm config set --location=project saves the setting to a pnpm-workspace.yaml file if no .npmrc file is present in the directory #9316.
Rename pnpm.allowNonAppliedPatches to pnpm.allowUnusedPatches. The old name is still supported but it would print a deprecation warning message.
Add pnpm.ignorePatchFailures to manage whether pnpm would ignore patch application failures.

If ignorePatchFailures is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.

If ignorePatchFailures is explicitly set to false, pnpm would throw an error when any type of patch fails to apply.

If ignorePatchFailures is explicitly set to true, pnpm would print a warning when any type of patch fails to apply.

Patch Changes

Remove dependency paths from audit output to prevent out-of-memory errors #9280.

`v10.6.5`

Compare Source

`v10.6.4`: pnpm 10.6.4

Compare Source

Patch Changes

Fix pnpm dlx with --allow-build flag #9263.
Invalid Node.js version in use-node-version should not cause pnpm itself to break #9276.
The max amount of workers running for linking packages from the store has been reduced to 4 to achieve optimal results #9286. The workers are performing many file system operations, so increasing the number of CPUs doesn't help performance after some point.

Platinum Sponsors

Gold Sponsors

`v10.6.3`

Compare Source

Patch Changes

pnpm install --prod=false should not crash, when executed in a project with a pnpm-workspace.yaml file #9233. This fixes regression introduced via #9211.
Add the missing node-options config to recursive run #9180.
Removed a branching code path that only executed when dedupe-peer-dependents=false. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that override dedupe-peer-dependents to false. There should be less unique bugs from turning off dedupe-peer-dependents.

See details in #9259.

`v10.6.2`

Compare Source

Patch Changes

pnpm self-update should always update the version in the packageManager field of package.json.
Fix running pnpm CLI from pnpm CLI on Windows when the CLI is bundled to an executable #8971.
pnpm patch-commit will now use the same filesystem as the store directory to compare and create patch files.
Don't show info output when --loglevel=error is used.
peerDependencyRules should be set in pnpm-workspace.yaml to take effect.

`v10.6.1`

Compare Source

Patch Changes

The pnpm CLI process should not stay hanging, when --silent reporting is used.
When --loglevel is set to error, don't show installation summary, execution time, and big tarball download progress.
Don't ignore pnpm.patchedDependencies from package.json #9226.
When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.
When a package version cannot be found in the package metadata, print the registry from which the package was fetched.

`v10.6.0`

Compare Source

Minor Changes

pnpm-workspace.yaml can now hold all the settings that .npmrc accepts. The settings should use camelCase #9211.

pnpm-workspace.yaml example:
```
verifyDepsBeforeRun: install
optimisticRepeatInstall: true
publicHoistPattern:
  - "*types*"
  - "!@&#8203;types/react"
```
Projects using a file: dependency on a local tarball file (i.e. .tgz, .tar.gz, .tar) will see a performance improvement during installation. Previously, using a file: dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.

Patch Changes

pnpm self-update should not leave a directory with a broken pnpm installation if the installation fails.
fast-glob replace with tinyglobby to reduce the size of the pnpm CLI dependencies #9169.
pnpm deploy should not remove fields from the deployed package's package.json file #9215.
pnpm self-update should not read the pnpm settings from the package.json file in the current working directory.
Fix pnpm deploy creating a package.json without the imports and license field #9193.
pnpm update -i should list only packages that have newer versions #9206.
Fix a bug causing entries in the catalogs section of the pnpm-lock.yaml file to be removed when dedupe-peer-dependents=false on a filtered install. #9112

`v10.5.2`

Compare Source

Patch Changes

The pnpm config set command should change the global .npmrc file by default.
This was a regression introduced by #9151 and shipped in pnpm v10.5.0.

`v10.5.1`

Compare Source

Patch Changes

Throw an error message if a pnpm-workspaces.yaml or pnpm-workspaces.yml file is found instead of a pnpm-workspace.yaml #9170.
Fix the update of pnpm-workspace.yaml by the pnpm approve-builds command #9168.
Normalize generated link paths in package.json #9163
Specifying overrides in pnpm-workspace.yaml should work.
pnpm dlx should ignore settings from the package.json file in the current working directory #9178.

`v10.5.0`

Compare Source

Minor Changes

Allow to set the "pnpm" settings from package.json via the pnpm-workspace.yaml file #9121.
Added support for automatically syncing files of injected workspace packages after pnpm run #9081. Use the sync-injected-deps-after-scripts setting to specify which scripts build the workspace package. This tells pnpm when syncing is needed. The setting should be defined in a .npmrc file at the root of the workspace. Example:
```
sync-injected-deps-after-scripts[]=compile
```
The packages field in pnpm-workspace.yaml became optional.

Patch Changes

pnpm link with no parameters should work as if --global is specified #9151.
Allow scope registry CLI option without --config. prefix such as --@scope:registry=https://scope.example.com/npm #9089.
pnpm link <path> should calculate relative path from the root of the workspace directory #9132.
Fix a bug causing catalog snapshots to be removed from the pnpm-lock.yaml file when using --fix-lockfile and --filter. #8639
Fix a bug causing catalog protocol dependencies to not re-resolve on a filtered install #8638.

`v10.4.1`

Compare Source

Patch Changes

Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #9105.
Print pnpm's version after the execution time at the end of the console output.
Print warning about ignored builds of dependencies on repeat install #9106.
Setting init-package-manager should work.

`v10.4.0`

Compare Source

Minor Changes

pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.
The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:
```
pnpm --allow-build=esbuild add bundle
```
This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

Related PR: #9086.
The pnpm init command adds a packageManager field with the current version of pnpm CLI #9069. To disable this behaviour, set the init-package-manager setting to false.

Patch Changes

pnpm approve-builds should work after two consecutive pnpm install runs #9083.
Fix instruction for updating pnpm with corepack #9101.
The pnpm version specified by packageManager cannot start with v.

`v10.3.0`

Compare Source

Minor Changes

Added a new setting called strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts) #9071.

Patch Changes

Fix a false negative of verify-deps-before-run after pnpm install --production|--no-optional #9019.
Print the warning about blocked installation scripts at the end of the installation output and make it more prominent.

microsoft/TypeScript (typescript)

`v5.8.2`

Compare Source

vuejs/language-tools (vue-tsc)

`v2.2.8`

Compare Source

Bug Fixes

revert "fix(language-core): validate v-model variable against model type"

`v2.2.6`

Compare Source

Features

feat(language-core): infer prop JSDoc from defineModel's leading comments (#5211) - Thanks to @KazariEX!

Bug Fixes

fix(language-core): map camelized prop name correctly (#5207) - Thanks to @KazariEX!
fix(component-meta): resolve defineModel options to collect default value (#5209) - Thanks to @KazariEX!
fix(language-core): avoid duplicate generation of defineExpose's codes - Thanks to @KazariEX!
fix(language-core): generate camelized prop name for defineModel (#5213) - Thanks to @KazariEX!
fix(language-core): validate v-model variable against model type (#5214) - Thanks to @KazariEX!
fix(language-core): use keywords instead of semicolons to separate script sections (#5217) - Thanks to @KazariEX!

Other Changes

ci: auto close issues with can't reproduce label - Thanks to @KazariEX!
refactor(language-core): defer the calculation of linkedCodeMappings offsets (#5220) - Thanks to @KazariEX!

`v2.2.4`

Compare Source

Features

feat(language-service): map sfc compiler errors outside the template inner content (#5045) - Thanks to @KazariEX!
feat(language-core): introduce options to control type inference of $attrs, $el, $refs and $slots (#5135) - Thanks to @KazariEX!
feat(language-core): enhance single root nodes collection (#4819) - Thanks to @KazariEX!

Bug Fixes

fix(language-core): move generateSfcBlockSection to the end to fix missing comma errors (#5184) - Thanks to @zhiyuanzmj!
fix(language-core): handle edge case of default slot name mismatch - Thanks to @KazariEX!
fix(language-core): combine dollar variable keys from the upper level interface - Thanks to @KazariEX!
fix(language-core): hoist the variables that may cause TS4081 (#5192) - Thanks to @KazariEX!
fix(language-core): adjust regex match for @vue-generic to improve offset calculation (#5193) - Thanks to @Gehbt!
fix(language-core): correct codegen of native element refs - Thanks to @KazariEX!
fix(language-core): ignore latex block content (#5151) - Thanks to @KazariEX!
fix(language-core): do not emit undefined for model with default value (#5198) - Thanks to @RylanBueckert-Broadsign!
fix(language-service): typescript-semantic renaming first in style blocks (#4685) - Thanks to @KazariEX!
fix(typescript-plugin): prevent removed components from appearing in the completion list - Thanks to @KazariEX!

Other Changes

refactor(language-core): drop invalid v-scope implemention - Thanks to @KazariEX!
refactor(language-core): improve type declaration of v-for - Thanks to @KazariEX!
test: enable declaration to track more errors - Thanks to @KazariEX!
refactor(language-core): remove semantic highlight of style module names - Thanks to @KazariEX!
chore(language-core): add docs for @vue-expect-error support (#5176) - Thanks to @machty!
ci: upload extension as artifact for each commit - Thanks to @KazariEX!

`v2.2.2`

Compare Source

Features

feat(language-core): navigation support for $attrs, $slots, $refs and $el in the template (#5056) - Thanks to @KazariEX!
feat(language-service): support global directives completion (#4989) - Thanks to @KazariEX!
feat(language-core): type support of useAttrs (#5106) - Thanks to @KazariEX!
feat(language-core): add options for fine-grained configuration of strictTemplates (#5138)
feat(language-service): display deprecated info of props in completion (#5134) - Thanks to @KazariEX!
feat(component-meta): collect destructured props defaults (#5101) - Thanks to @Akryum!
feat(language-core): add checkUnknownDirectives option (#5141) - Thanks to @KazariEX!
feat(language-core): support <script vapor> - Thanks to @KazariEX!

Bug Fixes

fix(language-core): ignore ts errors in function-scoped declare expressions (#5090) - Thanks to @zhiyuanzmj!
fix(language-core, typescript-plugin): handle self-reference component correctly (#5102) - Thanks to @KazariEX!
fix(language-core): do not generate element for <template> with v-slot (#5077) - Thanks to @KazariEX!
fix(language-service): set code action kinds to avoid warning (#5096) - Thanks to @KazariEX!
fix(language-core): handle parentheses in v-for exp
fix(language-core): slot exp formatting virtual code syntax incorrect
fix(language-core): arrow function formatting virtual code syntax incorrect in interpolation
fix(language-core): improve multiple lines event formatting result
fix(language-core): prefer loc.source instead of node content
fix(language-core): intersect local $attrs with __VLS_ctx.$attrs (#5113) - Thanks to @KazariEX!
fix(language-core): only generate model modifiers for components - Thanks to @KazariEX!
fix(language-plugin-pug): ignore duplicate attribute error of class (#5100) - Thanks to @KazariEX!
fix(language-core): align types of v-for with core (#5084) - Thanks to @KazariEX!
fix(language-core): map interpolation error with multiple variables correctly (#5158) - Thanks to @KazariEX!
fix(vscode): ask user to reload extension host when configuration changes (#5160) - Thanks to @typed-sigterm!
fix(typescript-plugin): update component names correctly for the first time - Thanks to @KazariEX!
fix(language-core): add undefined to first param type of optional model emits (#5171) - Thanks to @KazariEX!
fix(language-core): intersect __VLS_slots with __VLS_ctx.$slots (#5083) - Thanks to @KazariEX!
fix(language-core): complete codegen of slot name prop (#5139) - Thanks to @KazariEX!

Other Changes

refactor(language-service): read ast from codegen instead of parsing it repeatedly (#5086) - Thanks to @KazariEX!
refactor(language-core): rewrite vueCompilerOptions resolution logic
refactor(component-meta): read scriptSetupRanges from codegen - Thanks to @KazariEX!
refactor(component-meta): read node directly instead of creating sub ast - Thanks to @KazariEX!
refactor(component-meta): read ast from sfc.script - Thanks to @KazariEX!
refactor(language-core): generate the type of slots with function property (#5173) - Thanks to @KazariEX!
refactor(language-core): reduce codegen size of template returns - Thanks to @KazariEX!
refactor(language-core): remove semantic highlight of directives - Thanks to @KazariEX!
refactor: update alien-signals to 1.0.3 (#5181) - Thanks to @KazariEX!

`v2.2.0`

Compare Source

Features

feat(language-core): support @vue-generic (#4971) - Thanks to @KazariEX!
feat(vscode): add configuration for skipping automatic detection of Hybrid Mode (#5046) - Thanks to @KazariEX!
feat(language-service): crawl html data of data-allow-mismatch - Thanks to @KazariEX!
feat(language-core): type support of $attrs (#5076) - Thanks to @KazariEX!
feat(language-core): type support of useSlots and $slots (#5055) - Thanks to @KazariEX!
feat(language-core): type support of v-model modifiers (#5061) - Thanks to @KazariEX!
feat(language-service): process references data at runtime to reduce bundle size (#5054) - Thanks to @KazariEX!
feat(language-core): support the use of sfc root comment to configure vueCompilerOptions (#4987) - Thanks to @KazariEX!
feat(vscode): add timeout logic for insiders fetching (#5048) - Thanks to @KazariEX!
feat(vscode): add examples to inlay hints configuration (#5068) - Thanks to @KazariEX!

Performance

perf(typescript-plugin): use named pipe servers more efficiently (#5070)

Bug Fixes

fix(language-core): generate script setup starting from last leading comment without @ts-check - Thanks to @KazariEX!
fix(language-core): make model modifiers optional (#4978) - Thanks to @stafyniaksacha!
fix(language-core): always report missing props on <slot> (#4982) - Thanks to @KazariEX!
fix(language-core): avoid unchecked index access when parsing defineEmits (#5028) - Thanks to @KazariEX!
fix(language-service): handle text edit of special closing tags completion correctly (#5016) - Thanks to @KazariEX!
fix(language-core): don't generate variable access of template refs using useTemplateRef (#5032) - Thanks to @KazariEX!
fix(vscode): update enabledHybridMode before activate extension ([#5019](https://re

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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

codesandbox · 2024-11-18T22:02:12Z

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

vercel · 2024-11-18T22:02:14Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nuxt-new	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 28, 2025 10:55pm

renovate · 2025-03-28T22:55:08Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

renovate bot added dependencies devops labels Nov 18, 2024

renovate bot force-pushed the renovate/all-minor-patch branch from 69dc2cc to 014a886 Compare November 19, 2024 03:24

vercel bot temporarily deployed to Preview November 19, 2024 03:49 Inactive

vercel bot had a problem deploying to Preview November 19, 2024 03:49 Failure

vercel bot deployed to Preview November 19, 2024 03:49 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 014a886 to bb819dc Compare November 19, 2024 19:28

vercel bot temporarily deployed to Preview November 19, 2024 19:29 Inactive

vercel bot deployed to Preview November 19, 2024 19:29 View deployment

vercel bot had a problem deploying to Preview November 19, 2024 19:29 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from bb819dc to 0b01522 Compare November 20, 2024 00:42

renovate bot changed the title ~~chore(deps): update dependency @playwright/test to v1.49.0~~ chore(deps): update all non-major dependencies (minor) Nov 20, 2024

vercel bot temporarily deployed to Preview November 20, 2024 00:44 Inactive

vercel bot had a problem deploying to Preview November 20, 2024 00:44 Failure

vercel bot deployed to Preview November 20, 2024 00:44 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 0b01522 to 5f2e338 Compare November 20, 2024 14:11

vercel bot temporarily deployed to Preview November 20, 2024 14:13 Inactive

vercel bot deployed to Preview November 20, 2024 14:13 View deployment

vercel bot had a problem deploying to Preview November 20, 2024 14:13 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 5f2e338 to 84fdc27 Compare November 20, 2024 17:37

vercel bot temporarily deployed to Preview November 20, 2024 17:39 Inactive

vercel bot deployed to Preview November 20, 2024 17:39 View deployment

vercel bot had a problem deploying to Preview November 20, 2024 17:39 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 84fdc27 to 29e1b26 Compare November 21, 2024 11:16

vercel bot temporarily deployed to Preview November 21, 2024 11:18 Inactive

vercel bot had a problem deploying to Preview November 21, 2024 11:18 Failure

vercel bot deployed to Preview November 21, 2024 11:18 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 29e1b26 to e96939c Compare November 22, 2024 05:57

vercel bot had a problem deploying to Preview November 28, 2024 19:43 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 71f8854 to fd36765 Compare November 29, 2024 11:30

vercel bot had a problem deploying to Preview November 29, 2024 11:31 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from fd36765 to 7c4a06b Compare December 3, 2024 09:12

vercel bot had a problem deploying to Preview December 3, 2024 09:14 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 7c4a06b to 84abfb4 Compare December 3, 2024 12:59

vercel bot had a problem deploying to Preview December 3, 2024 13:00 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 84abfb4 to 984fe01 Compare December 3, 2024 19:02

vercel bot had a problem deploying to Preview December 3, 2024 19:03 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 984fe01 to 3e18146 Compare December 5, 2024 18:47

vercel bot had a problem deploying to Preview December 5, 2024 18:48 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 3e18146 to fa50b0e Compare December 6, 2024 17:27

vercel bot temporarily deployed to Preview December 6, 2024 17:34 Inactive

vercel bot had a problem deploying to Preview December 6, 2024 17:34 Failure

vercel bot deployed to Preview December 6, 2024 17:34 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from fa50b0e to dfc7cb1 Compare December 9, 2024 13:41

vercel bot temporarily deployed to Preview December 9, 2024 13:43 Inactive

vercel bot had a problem deploying to Preview December 9, 2024 13:43 Failure

vercel bot deployed to Preview December 9, 2024 13:43 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from dfc7cb1 to 2871ed0 Compare December 10, 2024 03:20

vercel bot temporarily deployed to Preview December 10, 2024 03:25 Inactive

vercel bot deployed to Preview December 10, 2024 03:25 View deployment

vercel bot had a problem deploying to Preview December 10, 2024 03:25 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 2871ed0 to c7be603 Compare December 16, 2024 12:04

vercel bot temporarily deployed to Preview December 16, 2024 12:08 Inactive

vercel bot had a problem deploying to Preview December 16, 2024 12:08 Failure

renovate bot and others added 2 commits March 26, 2025 13:52

chore(deps): update all non-major dependencies

34d2f6d

ci: update playwright image

b983e40

danielroe approved these changes Mar 28, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

chore(deps): update all non-major dependencies (minor)#293
danielroe merged 2 commits intomainfrom
renovate/all-minor-patch

renovate bot commented Nov 18, 2024 •

edited

Loading

Uh oh!

codesandbox bot commented Nov 18, 2024

Uh oh!

vercel bot commented Nov 18, 2024 •

edited

Loading

Uh oh!

renovate bot commented Mar 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate bot commented Nov 18, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

🚀 Features

🐛 Bug Fixes

👋 New Contributors

🚀 Features

🐛 Bug Fixes

New Contributors

🐞 Bug Fixes

Highlights

Browser Versions

Highlights

Browser Versions

Test runner

UI updates

Breaking

Browser Versions

Highlights

Browser Versions

Aria snapshots

Test runner

Breaking: channels chrome, msedge and similar switch to new headless

What do I need to do?

Other breaking changes

Try new Chromium headless

Miscellaneous

Browser Versions

Minor Changes

Patch Changes

v10.6.4: pnpm 10.6.4

Patch Changes

Platinum Sponsors

Gold Sponsors

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Bug Fixes

Features

Bug Fixes

Other Changes

Features

Bug Fixes

Other Changes

Features

Bug Fixes

Other Changes

Features

Performance

Bug Fixes

Configuration

Uh oh!

codesandbox bot commented Nov 18, 2024

Review or Edit in CodeSandbox

Uh oh!

vercel bot commented Nov 18, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate bot commented Mar 28, 2025

Edited/Blocked Notification

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

renovate bot commented Nov 18, 2024 •

edited

Loading

Breaking: channels `chrome`, `msedge` and similar switch to new headless

`v10.6.4`: pnpm 10.6.4

vercel bot commented Nov 18, 2024 •

edited

Loading