Update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@floatie/widget-nuxt	2.1.1 -> 2.2.0					dependencies	minor
@formkit/nuxt	1.6.5 -> 1.6.9					dependencies	patch
@formkit/themes (source)	1.6.5 -> 1.6.9					dependencies	patch
@iconify-json/ph	1.1.13 -> 1.2.2					dependencies	minor
@playwright/test (source)	1.44.1 -> 1.50.1					devDependencies	minor
@prisma/client (source)	6.0.0 -> 6.3.1					dependencies	minor
@tanstack/vue-query (source)	5.45.0 -> 5.66.0					dependencies	minor
@types/node (source)	22.10.1 -> 22.13.1					devDependencies	minor
@vueuse/components (source)	10.11.0 -> 10.11.1					dependencies	patch
@vueuse/core (source)	10.11.0 -> 10.11.1					devDependencies	patch
@vueuse/nuxt (source)	10.11.0 -> 10.11.1					devDependencies	patch
@vueuse/router (source)	10.11.0 -> 10.11.1					dependencies	patch
dotenv-cli	7.4.2 -> 7.4.4					devDependencies	patch
nanoid	5.0.7 -> 5.0.9					dependencies	patch
node (source)	22.12.0 -> 22.14.0						minor
nuxt (source)	3.12.2 -> 3.15.4					devDependencies	minor
pnpm (source)	9.4.0 -> 9.15.5					packageManager	minor
prisma (source)	6.0.0 -> 6.3.1					devDependencies	minor
typescript (source)	5.4.5 -> 5.7.3					dependencies	minor

---

Release Notes

floatie-io/widgets (@​floatie/widget-nuxt)

v2.1.7

Compare Source

v2.1.3

Compare Source

v2.1.2

Compare Source

formkit/formkit (@​formkit/nuxt)

v1.6.9

Compare Source

v1.6.8

Compare Source

🐛 Bug Fixes

• Now imports FormKitSchema automatically from @formkit/vue when autoImport is true in Nuxt (#​1286)
• Fixes a bug that caused falsey values to not reset properly (#​1509)

v1.6.7

Compare Source

🐛 Bug Fixes

• Fixes compatibility with Vue 3.5.6 (#​1501)
• Indicates compatibility with new v4 nuxt (#​1418)
• Fixes casing for the type prop of datetime-local input (#​1486)
• Keeps placeholder for null or undefined as well (#​1474)

💪 New features

• New validation rules date_before_or_equal, date_after_or_equal, date_before_node, date_after_node

v1.6.6

Compare Source

🐛 Bug fixes

• Fixes a bug that caused cleanup issues in Vue 3.5+ (#​1496).

formkit/formkit (@​formkit/themes)

v1.6.9

Compare Source

v1.6.8

Compare Source

🐛 Bug Fixes

• Now imports FormKitSchema automatically from @formkit/vue when autoImport is true in Nuxt (#​1286)
• Fixes a bug that caused falsey values to not reset properly (#​1509)

v1.6.7

Compare Source

🐛 Bug Fixes

• Fixes compatibility with Vue 3.5.6 (#​1501)
• Indicates compatibility with new v4 nuxt (#​1418)
• Fixes casing for the type prop of datetime-local input (#​1486)
• Keeps placeholder for null or undefined as well (#​1474)

💪 New features

• New validation rules date_before_or_equal, date_after_or_equal, date_before_node, date_after_node

v1.6.6

Compare Source

🐛 Bug fixes

• Fixes a bug that caused cleanup issues in Vue 3.5+ (#​1496).

microsoft/playwright (@​playwright/test)

v1.50.1

Compare Source

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.

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

v1.48.2

Compare Source

v1.48.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/33023 - [Bug]: command line flag --headed has no effect in ui modehttps://github.com/microsoft/playwright/issues/331077 - [REGRESSION]: page.waitForRequest does not get resolved since 1.48.https://github.com/microsoft/playwright/issues/3308585 - [Bug]: WebSocket route does not handle full URLs in Playwrighttps://github.com/microsoft/playwright/issues/33052052 - [Regression]: Inspector not showing recorded sthttps://github.com/microsoft/playwright/issues/331323132 - [Bug]: Wrong Ubuntu release name in Dockerfile.nhttps://github.com/microsoft/playwright/pull/3299632996 - [BUG] Trace attachments have small unusable height

Browser Versions

• Chromium 130.0.6723.19
• Mozilla Firefox 130.0
• WebKit 18.0

This version was also tested against the following stable channels:

• Google Chrome 129
• Microsoft Edge 129

v1.48.0

Compare Source

v1.47.2

Compare Source

Highlights

https://github.com/microsoft/playwright/pull/32699- [REGRESSION]: fix(codegen): use content_frame property in python/.NEThttps://github.com/microsoft/playwright/issues/327066- [REGRESSION]: page.pause() does not pause test timeout after 1.4https://github.com/microsoft/playwright/pull/3266161 - fix(trace-viewer): time delta between local and remote actions

Browser Versions

• Chromium 129.0.6668.29
• Mozilla Firefox 130.0
• WebKit 18.0

This version was also tested against the following stable channels:

• Google Chrome 128
• Microsoft Edge 128

v1.47.1

Compare Source

v1.47.0

Compare Source

v1.46.1

Compare Source

v1.46.0

Compare Source

v1.45.3

Compare Source

v1.45.2

Compare Source

v1.45.1

Compare Source

v1.45.0

Compare Source

prisma/prisma (@​prisma/client)

v6.3.1

Compare Source

This patch releases introduces improvements to the prisma init output when invoked to with the --db option.

Run npx prisma@latest init --db to get an instant Prisma Postgres database.

v6.3.0

Compare Source

Today, we are excited to share the 6.3.0 stable release 🎉

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Highlights

A brand new Prisma Studio

In this release we've included several great improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our release blog post, but here's a short list:

Prisma Studio is back in the Console

Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in the Prisma Console and is available for all PostgreSQL and MySQL databases.

A new model viewer

Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place.

A new editing experience

If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once.

Clean up at the click of a button

When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start.

Add limit to updateMany() and deleteMany()

Previously, limit has not existed as a valid option in top level updateMany() and deleteMany() queries. In 6.3.0 limit is now available in these queries, bringing their features more in line with other query types.

You can use limit like the following:

await prisma.user.deleteMany({
  where: { column: 'value' },
  limit: 100,
});

This will limit the number of deleted users to 100 at maximum.

Sort generator fields deterministically

In previous version of Prisma ORM, the fields inside of a generator block in your Prisma Schema were not deterministically sorted. This could lead to cases where prisma db pull could lead to re-ordering of fields.

In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first prisma db pull after you upgrade, but it will remain consistent afterwards.

Replace NOT IN with NOT EXISTS for PostgreSQL relation filters

In previous versions of Prisma ORM, when using the none or some relation filters, the SQL queries generated used NOT IN. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of IN with EXISTS in order to improve query performance.

A special thank you

We'd like to extend our heartfelt thanks to @​loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #​19249 and #​17303. Their insights and partnership have been invaluable in improving our product.

If your team could benefit from dedicated support and tailored solutions, learn more about our enterprise support plan.

Fixes and improvements

Prisma Client

• Add take or limit to updateMany() & deleteMany()

Prisma

• Prisma interactive transaction ignores DB exception on commit (with triggers)
• prisma db pull non-deterministically sorts generator fields
• no entry found for key error on views<->model relations
• Adding onUpdate data to the DMMF in @prisma/generator-helper

Credits

Huge thanks to @​WhyAsh5114 for their contributions to this release!

v6.2.1

Compare Source

Today we are releasing the 6.2.1 patch release to address an issue with some of the omitApi preview feature checks having been accidentally omitted when making the feature GA. Now it is fully functional without the preview feature flag.

Changes

• https://github.com/prisma/prisma/pull/25997

v6.2.0

Compare Source

Today we're releasing Prisma ORM version 6.2.0 🎉

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

We have a number of new features in this version, including support for json and enum fields in SQLite, a new updateManyAndReturn function, support for ULID values, as well as the promotion of the omit feature from Preview to Generally Availability.

Highlights

Excluding fields via omit is now production-ready

Our number one requested feature is out of Preview and Generally Available. In 6.2.0, you no longer need to add omitApi to your list of Preview features:

generator client {
  provider        = "prisma-client-js"
- previewFeatures = ["omitApi"]
}

As a refresher: omit allows you to exclude certain fields from being returned in the results of your Prisma Client queries.

You can either do this locally, on a per-query level:

const result = await prisma.user.findMany({
  omit: {
    password: true,
  },
});

Or globally, to ensure a field is excluded from all queries of a certain model:

const prisma = new PrismaClient({
  omit: {
    user: {
      password: true
    }
  }
})

// The password field is excluded in all queries, including this one
const user = await prisma.user.findUnique({ where: { id: 1 } })

For more information on omit, be sure to check our documentation.

json and enum fields in SQLite

Previous to this version, you could not define json and enum fields in your Prisma schema when using SQLite. The respective GitHub issues have been among the most popular ones in our repo, so with our new approach to open-source governance, we finally got to work and implemented these.

Working with JSON and Enum fields works similarly to other database providers, here’s an example:

datasource db {
  provider = "sqlite"
  url      = "file:./dev.db"
}

model User {
  id   Int    @​id @​default(autoincrement())
  name String
  role Role  
  data Json
}

enum Role {
  Customer
  Admin 
}

Support for auto-generated ULID values

Similar to cuid2 support released in ORM version 6.0.0, we are now adding support for Universally Unique Lexicographically Sortable Identifiers (or short: ULIDs 😄) in version 6.2.0. A ULID value is a 26-character alphanumeric string, e.g. 01GZ0GZ3XARH8ZP44A7TQ2W4ZD.

With this new feature, you can now create records with auto-generated ULID values for String fields:

model User {
  id String @​id @​default(ulid())  
}

New batch function: updateManyAndReturn

updateMany allows you to update many records in your database, but it only returns the count of the affected rows, not the resulting rows themselves. With updateManyAndReturn you are now able to achieve this:

const users = await prisma.user.updateManyAndReturn({
  where: {
    email: {
      contains: 'prisma.io',
    }
  },
  data: {
    role: 'ADMIN'
  }
})

This call to updateManyAndReturn will now return the actual records that have been updated in the query:

[{
  id: 22,
  name: 'Alice',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}, {
  id: 23,
  name: 'Bob',
  email: '[email protected]',
  profileViews: 0,
  role: 'ADMIN',
  coinflips: []
}]

Please note that like createManyAndReturn, updateManyAndReturn is only supported in PostgreSQL, CockroachDB, and SQLite.

Fixed runtime error in Node.js v23

While not officially supported, we understand that a lot of you like to be on the latest Node.js version — so we fixed an error that only occurred on Node.js 23. Happy coding ✌️

Prisma is hiring 🤝

Join us at Prisma to work on the most popular TypeScript ORM and other exciting products like the first serverless database built on unikernels!

We currently have two open roles in our Engineering team:

• Senior Software Engineer (Prisma ORM)
• Senior Software Engineer (Prisma Data Platform)

If these don’t fit, you can still check out our jobs page and send a general application.

v6.1.0

Compare Source

Today we're releasing Prisma ORM version 6.1.0

In this version our tracing Preview feature is being graduated to GA!

Highlights

Tracing goes GA

The tracing Preview feature is now stable. You now no longer have to include tracing in your set of enabled preview features.

generator client {
   provider        = "prisma-client-js"
-  previewFeatures = ["tracing"]
}

We have also changed some of the spans generated by Prisma Client. Previously, a trace would report the following spans:

prisma:client:operation
prisma:client:serialize
prisma:engine
prisma:engine:connection
prisma:engine:db_query
prisma:engine:serialize

Now, the following are reported:

prisma:client:operation
prisma:client:serialize
prisma:engine:query
prisma:engine:connection
prisma:engine:db_query
prisma:engine:serialize
prisma:engine:response_json_serialization

Additionally, we have made a few changes to our dependencies:

• @opentelemetry/api is now a peer dependency instead of a regular dependency
• registerInstrumentations in @opentelemetry/instrumentation is now re-exported by @prisma/instrumentation

After upgrading to Prisma ORM 6.1.0 you will need to add @opentelemetry/api to your dependencies if you haven't already:

npm install @​opentelemetry/api

You will also no longer need to have @opentelemetry/instrumentation if you only use registerInstrumentations. In this case you can import registerInstrumentations from @prisma/instrumentation

- import { PrismaInstrumentation } from '@​prisma/instrumentation'
+ import { PrismaInstrumentation, registerInstrumentations } from '@​prisma/instrumentation'

Bug fixes

Tracing related

As we're moving our tracing preview to GA, a number of issues have been resolved. Here are a few highlights:

• Tests for tracing expanded and improved
• Issues with Elastic APM addressed
• Issues with Datadog tracer addressed
• Prisma Client now respects suppressTracing

Other issues

We also have a number of other issues that were resolved outside of our tracing feature.

• Resolved type issues with the PrismaNeonHTTP adapter
• findUnique returns null when used instead of Promise.all
• Resolved an issue with the latest version of Alpine Linux

Fixes and improvements

Prisma

• Tracing: Detailed report and profiling informations
• Prisma Client Request Tracing Integration
• Instrumentation error in production: TypeError: parentTracer.getSpanLimits is not a function
• Prisma is using the internal Span constructor
• Prisma Client doesn't put all OTEL trace spans under one parent span
• Prisma trace has unaccounted time
• prisma:engine spans do not respect suppressTracing()
• tracing: engine spans don't pass through Sampler
• Add tests for tracing and different ways to open the first connection (including internal spans)
• Tracing: Long trailing delay in prisma:client:operation
• prisma:engine spans are missing when there are multiple new PrismaClient() invocations
• parentTracer.getSpanLimits is not a function
• Support tracers not derived from opentelemetry-sdk-trace-base (e.g. Datadog tracer)
• traceparent comments with multiple SQL statements
• Make @prisma/instrumentation dependencies peer dependencies
• Make sure db.statement attribute doesn't include the traceparent comment
• [Instrumentation] registerInstrumentations uses the global provider instead of the one passed in
• Instrumentation: Problems in working with Elastic APM
• PrismaNeonHTTP adapter breaks on some types e.g. timestamp
• Promise.all() returns null with findUnique()
• Alpine Linux 3.21: Prisma failed to detect the libssl/openssl version to use

Prisma Client

• Tracing operation duration bug under stress test
• @prisma/instrumentation Type Error: 'InstrumentionNodeModuleDefintion' is not generic

v6.0.1

Compare Source

TanStack/query (@​tanstack/vue-query)

v5.66.0

Compare Source

Version 5.66.0 - 1/31/25, 9:05 AM

Changes

Feat

• core: add client to queryFunctionContext (#​8599) (f86eb7e) by Dominik Dorfmeister

Docs

• Add OpenAPI Qraft React to the list of community projects (#​8588) (a507400) by Alex Batalov

Packages

• @​tanstack/eslint-plugin-query@​5.66.0
• @​tanstack/query-core@​5.66.0
• @​tanstack/query-persist-client-core@​5.66.0
• @​tanstack/angular-query-experimental@​5.66.0
• @​tanstack/query-async-storage-persister@​5.66.0
• @​tanstack/query-broadcast-client-experimental@​5.66.0
• @​tanstack/query-sync-storage-persister@​5.66.0
• @​tanstack/react-query@​5.66.0
• @​tanstack/react-query-devtools@​5.66.0
• @​tanstack/react-query-persist-client@​5.66.0
• @​tanstack/react-query-next-experimental@​5.66.0
• @​tanstack/solid-query@​5.66.0
• @​tanstack/solid-query-devtools@​5.66.0
• @​tanstack/solid-query-persist-client@​5.66.0
• @​tanstack/svelte-query@​5.66.0
• @​tanstack/svelte-query-devtools@​5.66.0
• @​tanstack/svelte-query-persist-client@​5.66.0
• @​tanstack/vue-query@​5.66.0
• @​tanstack/vue-query-devtools@​5.66.0
• @​tanstack/angular-query-devtools-experimental@​5.66.0

v5.65.0

Compare Source

Version 5.65.0 - 1/27/25, 4:19 PM

Changes

Feat

• types: type narrowing for isPlaceholderData (#​8586) (2399bb0) by Dominik Dorfmeister

Chore

• composite monorepo (#​8560) (97f5544) by Dominik Dorfmeister
• deps: update dependency vite to v5.4.12 [security] (#​8563) (4a0a129) by renovate[bot]

Ci

• bundle size preview (#​8577) (0613400) by Dominik Dorfmeister

Docs

• fix variables obtaining path (#​8589) (d595e23) by Oleksandr Danylchenko
• Document staleTime"s default (#​8561) (12d4542) by Alex Errant
• framework: update Next.js and Svelte documentation links (#​8572) (322760b) by @​ohansFavour
• fix invalid openapi-react-query url (#​8568) (cd88c9c) by Paul Nodet
• prefer using satisfies instead of type cast in persistQueryClient docs (#​8551) (397fcfc) by @​ruudandriessen

Packages

• @​tanstack/eslint-plugin-query@​5.65.0
• @​tanstack/query-async-storage-persister@​5.65.0
• @​tanstack/query-broadcast-client-experimental@​5.65.0
• @​tanstack/query-core@​5.65.0
• @​tanstack/query-devtools@​5.65.0
• @​tanstack/query-persist-client-core@​5.65.0
• @​tanstack/query-sync-storage-persister@​5.65.0
• @​tanstack/react-query@​5.65.0
• @​tanstack/react-query-devtools@​5.65.0
• @​tanstack/react-query-persist-client@​5.65.0
• @​tanstack/react-query-next-experimental@​5.65.0
• @​tanstack/solid-query@​5.65.0
• @​tanstack/solid-query-devtools@​5.65.0
• @​tanstack/solid-query-persist-client@​5.65.0
• @​tanstack/svelte-query@​5.65.0
• @​tanstack/svelte-query-devtools@​5.65.0
• @​tanstack/svelte-query-persist-client@​5.65.0
• @​tanstack/vue-query@​5.65.0
• @​tanstack/vue-query-devtools@​5.65.0
• @​tanstack/angular-query-devtools-experimental@​5.65.0
• @​tanstack/angular-query-experimental@​5.65.0

v5.64.2

Compare Source

Version 5.64.2 - 1/19/25, 8:45 AM

Changes

Fix

• react-query: add missing subscribed option to UseInfiniteQueryOptions (#​8546) (3e3fba9) by Seyed Mohammad Asadi

Chore

• deps: replace rimraf with premove ([#​8532](https://redirect.github.com/TanStack/query/issues

---

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 was generated by Mend Renovate. View the repository job log.