chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@auth/prisma-adapter (source)	2.9.0 -> 2.9.1
@prisma/client (source)	6.6.0 -> 6.8.2
@shikijs/transformers (source)	3.3.0 -> 3.4.2
@storybook/addon-a11y (source)	8.6.12 -> 8.6.14
@storybook/addon-essentials (source)	8.6.12 -> 8.6.14
@storybook/addon-interactions (source)	8.6.12 -> 8.6.14
@storybook/addon-links (source)	8.6.12 -> 8.6.14
@storybook/docs-tools (source)	8.6.12 -> 8.6.14
@storybook/react (source)	8.6.12 -> 8.6.14
@storybook/react-vite (source)	8.6.12 -> 8.6.14
@storybook/sveltekit (source)	8.6.12 -> 8.6.14
@sveltejs/adapter-auto (source)	6.0.0 -> 6.0.1
@sveltejs/kit (source)	2.20.8 -> 2.21.1
@testing-library/svelte	5.2.7 -> 5.2.8
@vitest/coverage-v8 (source)	3.1.2 -> 3.1.4
effect (source)	3.14.18 -> 3.16.2
flexsearch	0.8.158 -> 0.8.204
happy-dom	17.4.6 -> 17.5.6
lefthook	1.11.12 -> 1.11.13
lucide-react (source)	0.507.0 -> 0.511.0
lucide-solid (source)	0.507.0 -> 0.511.0
lucide-vue-next (source)	0.507.0 -> 0.511.0
match-sorter	8.0.1 -> 8.0.2
next (source)	15.3.1 -> 15.3.2
next-auth (source)	5.0.0-beta.27 -> 5.0.0-beta.28
nuxt (source)	3.17.2 -> 3.17.4
prettier-plugin-svelte	3.3.3 -> 3.4.0
prisma (source)	6.6.0 -> 6.8.2
react-hook-form (source)	7.56.2 -> 7.56.4
shiki (source)	3.3.0 -> 3.4.2
solid-js (source)	1.9.6 -> 1.9.7
storybook (source)	8.6.12 -> 8.6.14
svelte (source)	5.28.2 -> 5.33.9
svelte-check	4.1.7 -> 4.2.1
ts-pattern	5.7.0 -> 5.7.1
tsup (source)	8.4.0 -> 8.5.0
turbo (source)	2.5.2 -> 2.5.3
velite	0.2.2 -> 0.2.4
vercel (source)	41.7.0 -> 41.7.8
vite-plugin-dts	4.5.3 -> 4.5.4
vitest (source)	3.1.2 -> 3.1.4
vue (source)	3.5.13 -> 3.5.16

---

Release Notes

nextauthjs/next-auth (@​auth/prisma-adapter)

v2.9.1

Compare Source

Bugfixes

• adapter-prisma: import PrismaClientKnownRequestError for edge runtime compatibility (#​12755) (c7409f3)

prisma/prisma (@​prisma/client)

v6.8.2

Compare Source

Today, we are issuing the 6.8.2 patch release. It fully resolves an issue with the prisma init and prisma dev commands for some Windows users who were still facing problems after the previous incomplete fix in version 6.8.1.

Fixes:

• https://github.com/prisma/prisma/issues/27195

v6.8.1

Compare Source

Today, we are issuing the 6.8.1 patch release. It fixes an issue with the prisma init and prisma dev commands on Windows.

Fixes

• https://github.com/prisma/prisma/issues/27192

v6.8.0

Compare Source

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

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

Highlights

Local development with Prisma Postgres via prisma dev (Early Access)

In this release, we're releasing a way to develop against Prisma Postgres locally — no Docker required!

To get started, run the new prisma dev command:

npx prisma dev # starts a local Prisma Postgres server

This command spins up a local Prisma Postgres instance and prints the connection URL that you'll need to set as the url of your datasource block to point to a local Prisma Postgres instance. It looks similar to this:

datasource db {
  provider = "postgresql"
  url      = "prisma+postgres://localhost:51213/?api_key=ey..." 
}

You can then run migrations and execute queries against this local Prisma Postgres instance as with any remote one. Note that you need to keep the prisma dev process running in order to interact with the local Prisma Postgres instance.

📚 Learn more in the docs.

Native Deno support in prisma-client generator (Preview)

In this release, we're removing the deno Preview feature from the prisma-client-js generator. If you want to use Prisma ORM with Deno, you can now do so with the new prisma-client generator:

generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
  runtime = "deno"
}

📚 Learn more in the docs.

VS Code Agent Mode: AI support with your database workflows

Have you tried agent mode in VS Code already?

"The agent acts as an autonomous pair programmer that performs multi-step coding tasks at your command, such as analyzing your codebase, proposing file edits, and running terminal commands."

As of this release, your agent is capable of supporting you with your database workflows more than ever! If you're using VS Code and have the Prisma VS Code extension installed, your agent now is able to help you with your database workflows, such as:

• checking the status of your migrations (e.g. telling you if migrations haven't been applied)
• creating and running schema migrations for you
• authenticating you with the Prisma Console
• provisioning new Prisma Postgres instances so you can start coding right away

All you need to do is make sure you're using the latest version of Prisma's VS Code extension and your agent is ready to go 🚀

📚 Learn more in the docs.

Other news

You voted, we acted: New Singapore region for Prisma Postgres

We recently ran a poll where we asked you which region you'd like to see next for Prisma Postgres. The majority vote went to Asia Pacific (Singapore), so as of today, you're able to spin up new Prisma Postgres instances in the ap-southeast-1 region.

We're not stopping here — keep an eye out on X for another poll asking for your favorite regions that we should add!

v6.7.0

Compare Source

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

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

Highlights

Prisma ORM without Rust engines (Early Access)

If you're a regular visitor of our company blog, you may already know that we're currently working on moving the core of Prisma from Rust to TypeScript. We have written extensively about why we're moving away from Rust and already shared the first measurements of performance boosts we saw from the re-write.

This re-write is not just a move from one programming language to another. It fundamentally improves the architecture of Prisma ORM and replaces the Query Engine (which is written in Rust and deployed as a standalone binary) with a much leaner and more efficient approach that we call Query Compiler.

In this release, we're excited to give you Early Access to the new Query Compiler for PostgreSQL and SQLite database 🥳 Support for more database will follow very soon!

To use the new "Rust-free" version of Prisma ORM, add the queryCompiler (new) and driverAdapters feature flags to your client generator:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["queryCompiler", "driverAdapters"]
  output          = "../generated/prisma"
}

Now run prisma generate to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install one. For example, the one for PostgreSQL:

npm install @​prisma/adapter-pg

Once installed, you can instantiate PrismaClient as follows:

import { PrismaPg } from '@​prisma/adapter-pg'
import { PrismaClient } from './generated/prisma'

const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })
const prisma = new PrismaClient({ adapter })

This version of PrismaClient doesn't have a Query Engine binary and you can use it in the exact same way as before.

📚 Learn more in the docs.

Support for better-sqlite3 JavaScript driver (Preview)

Driver adapters are Prisma ORM's way of letting you use JS-native drivers (like pg) to interact with your database. In this release, we're introducing a new driver adapter for using the better-sqlite3 package, so you can now interact with SQLite database in a JS-native way.

To use it, first enable the driverAdapters Preview feature flag in on your client generator, then install these libraries:

npm install @​prisma/adapter-better-sqlite3

Now you can instantiate Prisma Client as follows:

import { PrismaBetterSQLite3 } from '@​prisma/adapter-better-sqlite3';
import { PrismaClient } from './generated/prisma';

const adapter = new PrismaBetterSQLite3({
  url: "file:./prisma/dev.db"
});
const prisma = new PrismaClient({ adapter });

📚 Learn more in the docs.

Multi-file Prisma schemas are now production-ready

The prismaSchemaFolder Preview feature is moving into General Availability 🎉 With that change, Prisma ORM now by default supports splitting your Prisma schema file and e.g. lets you organize your schema as follows:

prisma/schema.prisma → defines data source and generator

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

prisma/models/posts.prisma → defines Post model

model Post {
  id        Int     @​id @​default(autoincrement())
  title     String
  content   String?
  published Boolean @​default(false)
  author    User?   @​relation(fields: [authorId], references: [id])
  authorId  Int?
}

prisma/models/users.prisma → defines User model

model User {
  id    Int     @​id @​default(autoincrement())
  email String  @​unique
  name  String?
  posts Post[]
}

⚠️ Note that there have been breaking changes to the prismaSchemaFolder Preview feature in the last 6.6.0 release. If you've been using this feature to split your Prisma schema, make sure to read the release notes and update your project accordingly.

📚 Learn more in the docs.

Splitting generated output with new prisma-client generator (Preview)

With the prisma-client-js generator, the generated Prisma Client library is put into a single index.d.ts file. This sometimes led to issues with large schemas where the size of the generated output could slow down code editors and breaking auto-complete.

As of this release, our new prisma-client generator (that was released in 6.6.0) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file.

Also: As a bonus, we now ensure that generated files do not raise any ESLint and TypeScript errors!

Before

generated/
└── prisma
    ├── client.ts
    ├── index.ts # -> this is split into multiple files in 6.7.0
    └── libquery_engine-darwin.dylib.node

After

generated/
└── prisma
    ├── client.ts
    ├── commonInputTypes.ts
    ├── enums.ts
    ├── index.ts
    ├── internal
    │   ├── class.ts
    │   └── prismaNamespace.ts
    ├── libquery_engine-darwin.dylib.node
    ├── models
    │   ├── Post.ts
    │   └── User.ts
    └── models.ts

📚 Learn more in the docs.

Company news

Our team has been busy shipping more than just the ORM! Check out these articles to learn what else we've been up to recently:

• Announcing: Prisma Postgres Integration for Vercel Marketplace
• Securely Access Prisma Postgres from the Frontend (Early Access)
• Announcing Prisma's MCP Server: Vibe Code with Prisma Postgres

shikijs/shiki (@​shikijs/transformers)

v3.4.2

Compare Source

   🚀 Features

• markdown-it: Add langAlias option  -  by @​uncenter in https://github.com/shikijs/shiki/issues/1018 (97ff4)

    View changes on GitHub

v3.4.1

Compare Source

   🚀 Features

• rehype: Add langAlias option  -  by @​SoonIter in https://github.com/shikijs/shiki/issues/1015 (88d1a)
• transformers: transformerRemoveNotationEscape support rehype plugin usage  -  by @​fuma-nama in https://github.com/shikijs/shiki/issues/1011 (946ef)

   🐞 Bug Fixes

• vitepress-twoslash: Empty twoslash error at end of the line  -  by @​zzxming and @​antfu in https://github.com/shikijs/shiki/issues/999 (d27b5)

    View changes on GitHub

v3.4.0

Compare Source

   🐞 Bug Fixes

• Update deps and grammars  -  by @​antfu (310d1)

    View changes on GitHub

storybookjs/storybook (@​storybook/addon-a11y)

v8.6.14

Compare Source

• CLI: Add skip onboarding, recommended/minimal config - #​30930, thanks @​shilman!
• Core: Fix using dates in expect statements - #​28413, thanks @​yann-combarnous!
• React Native Web: Fix expo router by setting JSX to automatic - #​31484, thanks @​dannyhw!
• Test: Make sure that lit arrays are not cloned - #​31435, thanks @​kasperpeulen!

v8.6.13

Compare Source

• Controls: Fix boxShadow on empty controls - #​27193, thanks @​H0onnn!
• React Native Web: Update react-native-web - #​31324, thanks @​ndelangen!

storybookjs/storybook (@​storybook/addon-essentials)

v8.6.14

Compare Source

v8.6.13

Compare Source

storybookjs/storybook (@​storybook/addon-links)

v8.6.14

Compare Source

v8.6.13

Compare Source

sveltejs/kit (@​sveltejs/adapter-auto)

v6.0.1

Compare Source

Patch Changes

• chore: remove import-meta-resolve dependency (#​13629)

• Updated dependencies [bd1c04662332cbafa843c35a2e783486116af3d5, 09f61ec2a14573e27769edb403c58aea5433a39f, 09f61ec2a14573e27769edb403c58aea5433a39f]:

  • @​sveltejs/kit@​2.21.0

sveltejs/kit (@​sveltejs/kit)

v2.21.1

Compare Source

Patch Changes

• chore: clarify which functions handleFetch affects (#​13788)

• fix: ensure $env and $app/environment are correctly set while analysing server nodes (#​13790)

v2.21.0

Compare Source

Minor Changes

• feat: allow running client-side code at the top-level of universal pages/layouts when SSR is disabled and page options are only boolean or string literals (#​13684)

Patch Changes

• chore: remove import-meta-resolve dependency (#​13629)

• fix: remove component code from server nodes that are never used for SSR (#​13684)

testing-library/svelte-testing-library (@​testing-library/svelte)

v5.2.8

Compare Source

Bug Fixes

• configure dom-testing-library to flush Svelte changes (#​439) (492dbd1)

vitest-dev/vitest (@​vitest/coverage-v8)

v3.1.4

Compare Source

v3.1.3

Compare Source

   🐞 Bug Fixes

• Correctly resolve vitest import if inline: true is set  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7856 (a83f3)
• Fix fixture parsing with lowered async with esbuild 0.25.3  -  by @​hi-ogawa in https://github.com/vitest-dev/vitest/issues/7921 (c5c85)
• Remove event-catcher code  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7898 (deb1b)
• Reset mocks on test retry/repeat  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7897 (2fa76)
• Ignore failures on writeToCache  -  by @​orgads in https://github.com/vitest-dev/vitest/issues/7893 (8c7f7)
• browser: Correctly inherit CLI options  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/7858 (03660)
• deps: Update all non-major dependencies  -  in https://github.com/vitest-dev/vitest/issues/7867 (67ef7)
• reporters: --merge-reports to show each total run times  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/7877 (d613b)

    View changes on GitHub

Effect-TS/effect (effect)

v3.16.2

[Compare Source](https://redirect.github.com/Effect-TS/effect/compare/effect@3.16.1...ef

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

[vercel]

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

Name	Status	Preview	Updated (UTC)
ark-docs	❌ Failed (Inspect)		May 29, 2025 6:23pm

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/chakra-ui/ark/@ark-ui/react@3467

npm i https://pkg.pr.new/chakra-ui/ark/@ark-ui/solid@3467

npm i https://pkg.pr.new/chakra-ui/ark/@ark-ui/svelte@3467

npm i https://pkg.pr.new/chakra-ui/ark/@ark-ui/vue@3467

commit: 1da9fe6