danielhaus/danielhaus.de
danielhaus/danielhaus.de
2
1
Fork 0
Code Issues 1 Pull requests Projects Releases 19 Packages 1 Wiki Activity Actions

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

Merged
renovate-bot merged 1 commit from renovate/all-minor-patch into main 2026-09-05 01:02:25 +00:00
Conversation 1 Commits 1 Files changed 1 +1 -1
renovate-bot commented 2026-09-05 01:00:59 +00:00
Member
Copy link

This PR contains the following updates:

Package Change Age Confidence Type Update
@eslint/compat (source) 2.1.0 → 2.1.1 age confidence devDependencies patch
@playwright/test (source) 1.62.1 → 1.63.0 age confidence devDependencies minor
browserslist 4.28.8 → 4.28.9 age confidence devDependencies patch
eslint (source) 10.9.1 → 10.10.0 age confidence devDependencies minor
mcr.microsoft.com/playwright v1.62.1-noble → v1.63.0-noble age confidence container minor
playwright (source) 1.62.1 → 1.63.0 age confidence devDependencies minor
vitest-browser-svelte 3.0.0 → 3.1.0 age confidence devDependencies minor

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

eslint/rewrite (@​eslint/compat)

v2.1.1

Compare Source

Bug Fixes
  • preserve markVariableAsUsed return value in compat context (#​503) (66d9790)
microsoft/playwright (@​playwright/test)

v1.63.0

Compare Source

🔒 Test locks

Tests that access a shared resource — an external service, a global account setting — can now declare a named lock.
Tests that share a lock name never run concurrently, across files, workers and projects, while
everything else keeps running in parallel:

test('update user settings', { lock: 'user-settings' }, async ({ page }) => {
  // never runs at the same time as other tests holding 'user-settings'
});

A test can hold multiple locks, and test.describe() accepts a lock for the whole group.
Learn more about test locks.

🪟 Locate across frames

page.frameLocator() and frame.frameLocator() called without a selector search in any frame of the
subtree, so you no longer need to locate the iframe first:

// Finds the button in any frame on the page.
await page.frameLocator().getByRole('button').click();

The rest of the locator resolves inside a single frame, just like a regular locator, and an error is thrown when it
matches elements in several frames.

👁️ Visible-only locators

New locator.visible() returns a locator that matches only visible elements. It is the recommended
replacement for the :visible CSS pseudo-class:

await page.locator('button').visible().click();
🧾 Step params and subtitles

Steps now carry structured data for reporters. Playwright API steps report the target locator and call arguments,
and test.step() accepts subtitle and params options for your own steps:

await test.step('Login', async () => {
  // ...
}, { subtitle: 'as admin', params: { user: 'admin' } });

Reporters receive them via testStep.subtitle and testStep.params. For Playwright API
steps, the subtitle is the locator or the navigation url — for example, Click with subtitle getByRole('button').
Both are rendered next to the step title in the trace viewer and the HTML report.

🖼️ Aria and screen snapshots in traces

The snapshots option of tracing.start() and the testOptions.trace fixture option now accept an
object selecting what to capture on every action:

// playwright.config.ts
export default defineConfig({
  use: {
    trace: {
      mode: 'on',
      snapshots: { dom: true, aria: true, screen: true }
    },
  },
});

With aria and screen snapshots recorded, the new Display Aria mode in the trace viewer shows the action screenshot
side by side with the aria snapshot, and hovering an aria node highlights it on the screenshot.

New APIs
Browser and Context
Locators
const response = await request.get<User>('/api/users/42');
const user = await response.json(); // typed as User
Test runner
  • New standalone testOptions.reducedMotion, testOptions.forcedColors and testOptions.contrast options.
  • New --add-reporter command line option appends a reporter on top of the ones configured in playwright.config, instead of replacing them like --reporter does.
  • New omitTags option for the list, line, dot, github and junit reporters suppresses the tags that are automatically appended to test titles.
Command line
  • npx playwright install --no-remove keeps the browsers of other Playwright installations instead of removing them.
  • npx playwright codegen --http-credentials records against pages behind HTTP authentication.
Miscellaneous
  • New built-in perfetto reporter writes a Trace Event Format file for the Perfetto UI or chrome://tracing, rendering the test run as a timeline with a lane per worker.
  • The HTML report renders a duration waterfall next to test steps.
Announcements
  • ⚠️ The experimental @playwright/experimental-ct-react, @playwright/experimental-ct-react17 and @playwright/experimental-ct-vue packages will no longer be updated. Follow the migration guide to move to the stories model introduced in 1.62. Story ids passed to fixtures.mount() can now be typed through the generated Stories registry.
  • ⚠️ Ubuntu 20.04 is not supported anymore.
  • 🐧 On Linux arm64, Playwright now downloads the Chrome for Testing build of Chromium, the same build used on all other platforms.
Browser Versions
  • Chromium 153.0.8010.12
  • Mozilla Firefox 155.0
  • WebKit 26.6

This version was also tested against the following stable channels:

  • Google Chrome 153
  • Microsoft Edge 153
browserslist/browserslist (browserslist)

v4.28.9

Compare Source

eslint/eslint (eslint)

v10.10.0

Compare Source

Features

  • 264b434 feat: add d and v flags to no-unexpected-multiline (#​21305) (Gihyeon Jeong / 정기현)
  • c6cc6c5 feat: check Object.prototype property names in new-cap (#​21269) (crimsonjay0)
  • 5661fa6 feat: no-extra-bind false negatives with class fields and static blocks (#​21260) (synthex-byte)

Bug Fixes

  • bb47dc6 fix: update dependency file-entry-cache to v11 (#​20801) (Milos Djermanovic)
  • 427ac0a fix: use format strings in debug calls (#​21247) (Francesco Trotta)
  • 9d81532 fix: support __proto__ in /* exported */ comments (#​21261) (sethamus)
  • 87e0a08 fix: prefer-object-has-own autofix breaks when Object is shadowed (#​21282) (김채영)
  • 8e2cb14 fix: new-cap false positive for UTC calls with properties: false (#​21275) (Pixel)
  • 9f4a364 fix: Ignore static imports in no-unreachable (#​21276) (Taha Kotil)

Documentation

  • 2417cad docs: Update README (GitHub Actions Bot)
  • 9cecb8a docs: document \c control letter escapes in no-control-regex (#​21286) (한국)
  • 8724829 docs: update compat table links (#​21263) (fnx)
  • 5634542 docs: Clarify eqeqeq suggestion behavior (#​21256) (Müslüm Yılmaz)

Chores

vitest-community/vitest-browser-svelte (vitest-browser-svelte)

v3.1.0

Compare Source

   🚀 Features
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | Type | Update | |---|---|---|---|---|---| | [@eslint/compat](https://github.com/eslint/rewrite/tree/main/packages/compat#readme) ([source](https://github.com/eslint/rewrite/tree/HEAD/packages/compat)) | [`2.1.0` → `2.1.1`](https://renovatebot.com/diffs/npm/@eslint%2fcompat/2.1.0/2.1.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@eslint%2fcompat/2.1.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@eslint%2fcompat/2.1.0/2.1.1?slim=true) | devDependencies | patch | | [@playwright/test](https://playwright.dev) ([source](https://github.com/microsoft/playwright)) | [`1.62.1` → `1.63.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.62.1/1.63.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@playwright%2ftest/1.63.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@playwright%2ftest/1.62.1/1.63.0?slim=true) | devDependencies | minor | | [browserslist](https://github.com/browserslist/browserslist) | [`4.28.8` → `4.28.9`](https://renovatebot.com/diffs/npm/browserslist/4.28.8/4.28.9) | ![age](https://developer.mend.io/api/mc/badges/age/npm/browserslist/4.28.9?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/browserslist/4.28.8/4.28.9?slim=true) | devDependencies | patch | | [eslint](https://eslint.org) ([source](https://github.com/eslint/eslint)) | [`10.9.1` → `10.10.0`](https://renovatebot.com/diffs/npm/eslint/10.9.1/10.10.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/eslint/10.10.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/eslint/10.9.1/10.10.0?slim=true) | devDependencies | minor | | mcr.microsoft.com/playwright | `v1.62.1-noble` → `v1.63.0-noble` | ![age](https://developer.mend.io/api/mc/badges/age/docker/mcr.microsoft.com%2fplaywright/v1.63.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/docker/mcr.microsoft.com%2fplaywright/v1.62.1/v1.63.0?slim=true) | container | minor | | [playwright](https://playwright.dev) ([source](https://github.com/microsoft/playwright)) | [`1.62.1` → `1.63.0`](https://renovatebot.com/diffs/npm/playwright/1.62.1/1.63.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/playwright/1.63.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/playwright/1.62.1/1.63.0?slim=true) | devDependencies | minor | | [vitest-browser-svelte](https://github.com/vitest-community/vitest-browser-svelte) | [`3.0.0` → `3.1.0`](https://renovatebot.com/diffs/npm/vitest-browser-svelte/3.0.0/3.1.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/vitest-browser-svelte/3.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/vitest-browser-svelte/3.0.0/3.1.0?slim=true) | devDependencies | minor | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/121) for more information. --- ### Release Notes <details> <summary>eslint/rewrite (@&#8203;eslint/compat)</summary> ### [`v2.1.1`](https://github.com/eslint/rewrite/blob/HEAD/packages/compat/CHANGELOG.md#211-2026-09-01) [Compare Source](https://github.com/eslint/rewrite/compare/b8949534bf7f498d941007f3adc2740157965b49...a4466ca3f8dc7d6817c4dd91c10a989b83ecb30d) ##### Bug Fixes - preserve markVariableAsUsed return value in compat context ([#&#8203;503](https://github.com/eslint/rewrite/issues/503)) ([66d9790](https://github.com/eslint/rewrite/commit/66d97901b70918438deb4355b730079e4d087889)) </details> <details> <summary>microsoft/playwright (@&#8203;playwright/test)</summary> ### [`v1.63.0`](https://github.com/microsoft/playwright/releases/tag/v1.63.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.62.1...v1.63.0) ##### 🔒 Test locks Tests that access a shared resource — an external service, a global account setting — can now declare a named `lock`. Tests that share a lock name never run concurrently, across files, workers and [projects](https://playwright.dev/docs/test-projects), while everything else keeps running in parallel: ```js test('update user settings', { lock: 'user-settings' }, async ({ page }) => { // never runs at the same time as other tests holding 'user-settings' }); ``` A test can hold multiple locks, and [test.describe()](https://playwright.dev/docs/api/class-test#test-describe) accepts a `lock` for the whole group. Learn more about [test locks](https://playwright.dev/docs/test-parallel#test-locks). ##### 🪟 Locate across frames [page.frameLocator()](https://playwright.dev/docs/api/class-page#page-frame-locator) and [frame.frameLocator()](https://playwright.dev/docs/api/class-frame#frame-frame-locator) called without a selector search in any frame of the subtree, so you no longer need to locate the iframe first: ```js // Finds the button in any frame on the page. await page.frameLocator().getByRole('button').click(); ``` The rest of the locator resolves inside a single frame, just like a regular locator, and an error is thrown when it matches elements in several frames. ##### 👁️ Visible-only locators New [locator.visible()](https://playwright.dev/docs/api/class-locator#locator-visible) returns a locator that matches only visible elements. It is the recommended replacement for the `:visible` CSS pseudo-class: ```js await page.locator('button').visible().click(); ``` ##### 🧾 Step params and subtitles Steps now carry structured data for reporters. Playwright API steps report the target locator and call arguments, and [test.step()](https://playwright.dev/docs/api/class-test#test-step) accepts `subtitle` and `params` options for your own steps: ```js await test.step('Login', async () => { // ... }, { subtitle: 'as admin', params: { user: 'admin' } }); ``` Reporters receive them via [testStep.subtitle](https://playwright.dev/docs/api/class-teststep#test-step-subtitle) and [testStep.params](https://playwright.dev/docs/api/class-teststep#test-step-params). For Playwright API steps, the subtitle is the locator or the navigation url — for example, `Click` with subtitle `getByRole('button')`. Both are rendered next to the step title in the trace viewer and the HTML report. ##### 🖼️ Aria and screen snapshots in traces The `snapshots` option of [tracing.start()](https://playwright.dev/docs/api/class-tracing#tracing-start) and the [testOptions.trace](https://playwright.dev/docs/api/class-testoptions#test-options-trace) fixture option now accept an object selecting what to capture on every action: ```js // playwright.config.ts export default defineConfig({ use: { trace: { mode: 'on', snapshots: { dom: true, aria: true, screen: true } }, }, }); ``` With aria and screen snapshots recorded, the new **Display Aria** mode in the trace viewer shows the action screenshot side by side with the aria snapshot, and hovering an aria node highlights it on the screenshot. ##### New APIs ##### Browser and Context - [`httpCredentials`](https://playwright.dev/docs/api/class-browser#browser-new-context-option-http-credentials) now also accepts an array of credentials. The first entry matching the request origin is used, and entries without an origin match any request. - New option [`opfs`](https://playwright.dev/docs/api/class-browsercontext#browser-context-storage-state-option-opfs) includes the [origin private file system](https://developer.mozilla.org/en-US/docs/Web/API/File_System_API/Origin_private_file_system) in the storage state, so it can be persisted and restored into later contexts. - New events [page.on('dialogclosed')](https://playwright.dev/docs/api/class-page#page-event-dialog-closed) and [browserContext.on('dialogclosed')](https://playwright.dev/docs/api/class-browsercontext#browser-context-event-dialog-closed) are emitted when a JavaScript dialog is accepted, dismissed or closed by the user. ##### Locators - New [locator.ariaSnapshotJSON()](https://playwright.dev/docs/api/class-locator#locator-aria-snapshot-json) and [page.ariaSnapshotJSON()](https://playwright.dev/docs/api/class-page#page-aria-snapshot-json) return the aria snapshot as a JSON value instead of YAML markup, with `mode`, `depth` and `boxes` options. - [apiRequestContext.get()](https://playwright.dev/docs/api/class-apirequestcontext#api-request-context-get) and other request methods accept a type argument that types the response `json()`: ```js const response = await request.get<User>('/api/users/42'); const user = await response.json(); // typed as User ``` ##### Test runner - New standalone [testOptions.reducedMotion](https://playwright.dev/docs/api/class-testoptions#test-options-reduced-motion), [testOptions.forcedColors](https://playwright.dev/docs/api/class-testoptions#test-options-forced-colors) and [testOptions.contrast](https://playwright.dev/docs/api/class-testoptions#test-options-contrast) options. - New `--add-reporter` command line option appends a reporter on top of the ones configured in `playwright.config`, instead of replacing them like `--reporter` does. - New `omitTags` option for the `list`, `line`, `dot`, `github` and `junit` reporters suppresses the tags that are automatically appended to test titles. ##### Command line - `npx playwright install --no-remove` keeps the browsers of other Playwright installations instead of removing them. - `npx playwright codegen --http-credentials` records against pages behind HTTP authentication. ##### Miscellaneous - New built-in [`perfetto`](https://playwright.dev/docs/test-reporters#perfetto-reporter) reporter writes a Trace Event Format file for the [Perfetto UI](https://ui.perfetto.dev) or `chrome://tracing`, rendering the test run as a timeline with a lane per worker. - The HTML report renders a duration waterfall next to test steps. ##### Announcements - ⚠️ The experimental `@playwright/experimental-ct-react`, `@playwright/experimental-ct-react17` and `@playwright/experimental-ct-vue` packages will no longer be updated. Follow the [migration guide](https://playwright.dev/docs/test-components#migration-from-the-experimental-packages) to move to the stories model introduced in 1.62. Story ids passed to [fixtures.mount()](https://playwright.dev/docs/api/class-fixtures#fixtures-mount) can now be typed through the generated `Stories` registry. - ⚠️ Ubuntu 20.04 is not supported anymore. - 🐧 On Linux arm64, Playwright now downloads the [Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing) build of Chromium, the same build used on all other platforms. ##### Browser Versions - Chromium 153.0.8010.12 - Mozilla Firefox 155.0 - WebKit 26.6 This version was also tested against the following stable channels: - Google Chrome 153 - Microsoft Edge 153 </details> <details> <summary>browserslist/browserslist (browserslist)</summary> ### [`v4.28.9`](https://github.com/browserslist/browserslist/blob/HEAD/CHANGELOG.md#4289) [Compare Source](https://github.com/browserslist/browserslist/compare/4.28.8...4.28.9) - Improve `or` parsing performance (by [@&#8203;NotAFlightRisk](https://github.com/NotAFlightRisk)). </details> <details> <summary>eslint/eslint (eslint)</summary> ### [`v10.10.0`](https://github.com/eslint/eslint/releases/tag/v10.10.0) [Compare Source](https://github.com/eslint/eslint/compare/v10.9.1...v10.10.0) #### Features - [`264b434`](https://github.com/eslint/eslint/commit/264b4346d1963701df0c398b4aeb2f6e8b2af93e) feat: add `d` and `v` flags to `no-unexpected-multiline` ([#&#8203;21305](https://github.com/eslint/eslint/issues/21305)) (Gihyeon Jeong / 정기현) - [`c6cc6c5`](https://github.com/eslint/eslint/commit/c6cc6c592f30901345d94ef75e0d42c1894fae6c) feat: check `Object.prototype` property names in `new-cap` ([#&#8203;21269](https://github.com/eslint/eslint/issues/21269)) (crimsonjay0) - [`5661fa6`](https://github.com/eslint/eslint/commit/5661fa65fde9fd4c14f0b730e3cee6a42fc657c1) feat: no-extra-bind false negatives with class fields and static blocks ([#&#8203;21260](https://github.com/eslint/eslint/issues/21260)) (synthex-byte) #### Bug Fixes - [`bb47dc6`](https://github.com/eslint/eslint/commit/bb47dc6da2399a8f76c0c0c3273e6bc314c480e5) fix: update dependency file-entry-cache to v11 ([#&#8203;20801](https://github.com/eslint/eslint/issues/20801)) (Milos Djermanovic) - [`427ac0a`](https://github.com/eslint/eslint/commit/427ac0a014066c36aa57fa8fa9af20fd9fb591e1) fix: use format strings in debug calls ([#&#8203;21247](https://github.com/eslint/eslint/issues/21247)) (Francesco Trotta) - [`9d81532`](https://github.com/eslint/eslint/commit/9d8153223dbf47b9aecdc1474202aaee4845f146) fix: support `__proto__` in `/* exported */` comments ([#&#8203;21261](https://github.com/eslint/eslint/issues/21261)) (sethamus) - [`87e0a08`](https://github.com/eslint/eslint/commit/87e0a082438264ad90b87fd74165ab4fd90f63ef) fix: prefer-object-has-own autofix breaks when Object is shadowed ([#&#8203;21282](https://github.com/eslint/eslint/issues/21282)) (김채영) - [`8e2cb14`](https://github.com/eslint/eslint/commit/8e2cb142217f2efee1d10dcc02bfb75145ae775d) fix: `new-cap` false positive for `UTC` calls with `properties: false` ([#&#8203;21275](https://github.com/eslint/eslint/issues/21275)) (Pixel) - [`9f4a364`](https://github.com/eslint/eslint/commit/9f4a364ab0ade048dfce1f37792b1d461d866e55) fix: Ignore static imports in no-unreachable ([#&#8203;21276](https://github.com/eslint/eslint/issues/21276)) (Taha Kotil) #### Documentation - [`2417cad`](https://github.com/eslint/eslint/commit/2417cad57d7d1bc4cf3ecf0f0575cfb10ff2011c) docs: Update README (GitHub Actions Bot) - [`9cecb8a`](https://github.com/eslint/eslint/commit/9cecb8a0a2348070abf72321965d41919c7cc626) docs: document `\c` control letter escapes in no-control-regex ([#&#8203;21286](https://github.com/eslint/eslint/issues/21286)) (한국) - [`8724829`](https://github.com/eslint/eslint/commit/8724829f69f8ed80c876e3a5a017da199ce78739) docs: update compat table links ([#&#8203;21263](https://github.com/eslint/eslint/issues/21263)) (fnx) - [`5634542`](https://github.com/eslint/eslint/commit/5634542be580750ffb1a5766470f9e9c72719696) docs: Clarify eqeqeq suggestion behavior ([#&#8203;21256](https://github.com/eslint/eslint/issues/21256)) (Müslüm Yılmaz) #### Chores - [`b3d876b`](https://github.com/eslint/eslint/commit/b3d876b46083d67899eb1d9613118c1c583632a2) chore: disable npm audit in ecosystem tests ([#&#8203;21306](https://github.com/eslint/eslint/issues/21306)) (Francesco Trotta) - [`1696682`](https://github.com/eslint/eslint/commit/1696682791661c13167eb905da2f38d1b8f4a3bf) ci: restore EMFILE test on Node.js 26 ([#&#8203;21297](https://github.com/eslint/eslint/issues/21297)) (Marry (Subin Yang)) - [`2c7f5d6`](https://github.com/eslint/eslint/commit/2c7f5d6f47a92e8c0847af103e40fdb2f4dc61ef) chore: update github/codeql-action action to v4.37.9 ([#&#8203;21296](https://github.com/eslint/eslint/issues/21296)) (renovate\[bot]) - [`3c753f1`](https://github.com/eslint/eslint/commit/3c753f18b461bfbf36d41a79a7863c093ef48489) chore: update eslint ([#&#8203;21289](https://github.com/eslint/eslint/issues/21289)) (renovate\[bot]) - [`1c73469`](https://github.com/eslint/eslint/commit/1c734690bf6f4f9c542bec428d5a1a5c6cc4a19b) chore: update ecosystem plugins ([#&#8203;21280](https://github.com/eslint/eslint/issues/21280)) (ESLint Bot) - [`08a02be`](https://github.com/eslint/eslint/commit/08a02be429e21fc93d86c8dd16cec6dc945ea2c1) test: add error locations to `no-extra-boolean-cast` ([#&#8203;21266](https://github.com/eslint/eslint/issues/21266)) (lumir) - [`77bb1db`](https://github.com/eslint/eslint/commit/77bb1db8e730b7da2347c647d60f215706aa349a) chore: update github/codeql-action action to v4.37.8 ([#&#8203;21270](https://github.com/eslint/eslint/issues/21270)) (renovate\[bot]) - [`007e81a`](https://github.com/eslint/eslint/commit/007e81ac0ad66bd0be4887d88a276df292ae0bed) ci: skip EMFILE test on Node.js 26 ([#&#8203;21265](https://github.com/eslint/eslint/issues/21265)) (lumir) - [`0430280`](https://github.com/eslint/eslint/commit/0430280e7cca9dc0fdbf0bc50464e98e84285c49) chore: improve ecosystem tests compatibility on Windows ([#&#8203;21178](https://github.com/eslint/eslint/issues/21178)) (crimsonjay0) </details> <details> <summary>vitest-community/vitest-browser-svelte (vitest-browser-svelte)</summary> ### [`v3.1.0`](https://github.com/vitest-community/vitest-browser-svelte/releases/tag/v3.1.0) [Compare Source](https://github.com/vitest-community/vitest-browser-svelte/compare/v3.0.0...v3.1.0) #####    🚀 Features - Add license and support vitest 5  -  by [@&#8203;sheremet-va](https://github.com/sheremet-va) in [#&#8203;45](https://github.com/vitest-community/vitest-browser-svelte/issues/45) [<samp>(67c45)</samp>](https://github.com/vitest-community/vitest-browser-svelte/commit/67c457e) #####     [View changes on GitHub](https://github.com/vitest-community/vitest-browser-svelte/compare/v3.0.0...v3.1.0) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My40My4yIiwidXBkYXRlZEluVmVyIjoiNDMuNDMuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
chore(deps): update all non-major dependencies
Some checks failed
renovate/artifacts Artifact file update failure
Build / Test (pull_request) Failing after 1m10s
Details
Build / Build (pull_request) Has been skipped
Details
e9dd9b2482
renovate-bot scheduled this pull request to auto merge when all checks succeed 2026-09-05 01:01:00 +00:00
renovate-bot commented 2026-09-05 01:01:00 +00:00
Author
Member
Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: danielhaus.de@1.10.1
npm error Found: @vitest/browser-playwright@4.1.11
npm error node_modules/@vitest/browser-playwright
npm error   peerOptional @vitest/browser-playwright@"4.1.11" from vitest@4.1.11
npm error   node_modules/vitest
npm error     peerOptional vitest@"*" from @testing-library/svelte@5.4.2
npm error     node_modules/@testing-library/svelte
npm error       dev @testing-library/svelte@"^5.4.2" from the root project
npm error     peer vitest@"4.1.11" from @vitest/browser@4.1.11
npm error     node_modules/@vitest/browser
npm error       @vitest/browser@"4.1.11" from @vitest/browser-playwright@4.1.11
npm error     2 more (@vitest/browser-playwright, the root project)
npm error   dev @vitest/browser-playwright@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error dev @vitest/browser-playwright@"^5.0.0" from the root project
npm error
npm error Conflicting peer dependency: vitest@5.0.0
npm error node_modules/vitest
npm error   peer vitest@"5.0.0" from @vitest/browser-playwright@5.0.0
npm error   node_modules/@vitest/browser-playwright
npm error     dev @vitest/browser-playwright@"^5.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-09-05T01_00_41_042Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-09-05T01_00_41_042Z-debug-0.log
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: package-lock.json ``` npm warn Unknown env config "store". This will stop working in the next major version of npm. npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While resolving: danielhaus.de@1.10.1 npm error Found: @vitest/browser-playwright@4.1.11 npm error node_modules/@vitest/browser-playwright npm error peerOptional @vitest/browser-playwright@"4.1.11" from vitest@4.1.11 npm error node_modules/vitest npm error peerOptional vitest@"*" from @testing-library/svelte@5.4.2 npm error node_modules/@testing-library/svelte npm error dev @testing-library/svelte@"^5.4.2" from the root project npm error peer vitest@"4.1.11" from @vitest/browser@4.1.11 npm error node_modules/@vitest/browser npm error @vitest/browser@"4.1.11" from @vitest/browser-playwright@4.1.11 npm error 2 more (@vitest/browser-playwright, the root project) npm error dev @vitest/browser-playwright@"^5.0.0" from the root project npm error npm error Could not resolve dependency: npm error dev @vitest/browser-playwright@"^5.0.0" from the root project npm error npm error Conflicting peer dependency: vitest@5.0.0 npm error node_modules/vitest npm error peer vitest@"5.0.0" from @vitest/browser-playwright@5.0.0 npm error node_modules/@vitest/browser-playwright npm error dev @vitest/browser-playwright@"^5.0.0" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /tmp/renovate/cache/others/npm/_logs/2026-09-05T01_00_41_042Z-eresolve-report.txt npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-09-05T01_00_41_042Z-debug-0.log ```
renovate-bot deleted branch renovate/all-minor-patch 2026-09-05 01:02:25 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
bug
Something is not working

  
duplicate
This issue or pull request already exists

  
enhancement
New feature

  
help wanted
Need some help

  
invalid
Something is wrong

  
question
More information is needed

  
wontfix
This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
danielhaus/danielhaus.de!172
No description provided.