Update all dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
@hookform/resolvers (source)	3.3.4 -> 3.4.2					dependencies	minor
@prisma/client (source)	5.11.0 -> 5.14.0					dependencies	minor
@types/node (source)	20.11.30 -> 20.12.13					devDependencies	minor
@types/react (source)	18.2.67 -> 18.3.3					devDependencies	minor
@types/react-dom (source)	18.2.22 -> 18.3.0					devDependencies	minor
KengoTODA/actions-setup-docker-compose	v1.2.1 -> v1.2.2					action	patch
autoprefixer	10.4.18 -> 10.4.19					devDependencies	patch
clsx	2.1.0 -> 2.1.1					dependencies	patch
cypress (source)	13.7.0 -> 13.10.0					devDependencies	minor
dayjs (source)	1.11.10 -> 1.11.11					dependencies	patch
eslint-config-next (source)	14.1.3 -> 14.2.3					devDependencies	minor
eslint-plugin-cypress	2.15.1 -> 2.15.2					devDependencies	patch
eslint-plugin-react	7.34.1 -> 7.34.2					devDependencies	patch
eslint-plugin-react-hooks (source)	4.6.0 -> 4.6.2					devDependencies	patch
eslint-plugin-sonarjs	^0.24.0 -> ^0.25.0					devDependencies	minor
geist (source)	1.2.2 -> 1.3.0					dependencies	minor
lucia (source)	3.1.1 -> 3.2.0					dependencies	minor
lucide-react (source)	^0.359.0 -> ^0.381.0					dependencies	minor
mocha (source)	10.3.0 -> 10.4.0					devDependencies	minor
next (source)	14.1.3 -> 14.2.3					dependencies	minor
oslo	1.1.3 -> 1.2.0					dependencies	minor
postcss (source)	8.4.36 -> 8.4.38					devDependencies	patch
postgres	16.2-alpine -> 16.3-alpine						minor
prisma (source)	5.11.0 -> 5.14.0					dependencies	minor
react (source)	18.2.0 -> 18.3.1					dependencies	minor
react-dom (source)	18.2.0 -> 18.3.1					dependencies	minor
react-hook-form (source)	7.51.1 -> 7.51.5					dependencies	patch
tailwind-merge	2.2.2 -> 2.3.0					dependencies	minor
tailwindcss (source)	3.4.1 -> 3.4.3					devDependencies	patch
typescript (source)	5.4.2 -> 5.4.5					devDependencies	patch
vitest (source)	1.4.0 -> 1.6.0					devDependencies	minor
zod (source)	3.22.4 -> 3.23.8					dependencies	minor

---

Release Notes

react-hook-form/resolvers (@​hookform/resolvers)

v3.4.2

Compare Source

Bug Fixes

• move back to in-build set and remove lodash.set (#​685) (5754c47)

v3.4.1

Compare Source

Bug Fixes

• migrate set to lodash.set package (#​684) (bdc1f1f)

v3.4.0

Compare Source

prisma/prisma (@​prisma/client)

v5.14.0

Compare Source

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

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

Highlights

Share your feedback about Prisma ORM

We want to know how you like working with Prisma ORM in your projects! Please take our 2min survey and let us know what you like or where we can improve 🙏

createManyAndReturn()

We’re happy to announce the availability of a new, top-level Prisma Client query: createManyAndReturn(). It works similarly to createMany() but uses a RETURNING clause in the SQL query to retrieve the records that were just created.

Here’s an example of creating multiple posts and then immediately returning those posts.

const postBodies = req.json()['posts']

const posts = prisma.post.createManyAndReturn({
	data: postBodies
});

return posts

Additionally,createManyAndReturn() supports the same options as findMany(), such as the ability to return only specific fields.

const postBodies = req.json()['posts']

const postTitles = prisma.post.createManyAndReturn({
	data: postBodies,
	select: {
	  title: true,
	},
});

return postTitles

Note: Because createManyAndReturn() uses the RETURNING clause, it is only supported by PostgreSQL, CockroachDB, and SQLite databases. At this time, relationLoadStrategy: join is not supported in createManyAndReturn() queries.

MongoDB performance improvements

Previously, Prisma ORM suffered from performance issues when using the in operator or when including related models in queries against a MongoDB database. These queries were translated by the Prisma query engine in such a way that indexes were skipped and collection scans were used, leading to slower queries especially on large datasets.

With 5.14.0, Prisma ORM now rewrites queries to use a combination of $or and $eq operators, leading to dramatic performance increases for queries that include in operators or relation loading.

Fixes and improvements

Prisma Client

• createMany() should return the created records
• Generating Prisma client without any model in its schema
• MongoDB: Performance issue with nested take on many-to-one relationship
• Slow queries on MongoDB using include for relations
• [MongoDB] Performance issue in findMany() query execution with in
• MongoDB nested/include query slow
• MongoDB Connector generates queries which do not take advantage of indices.
• Mongodb Nested Queries Not Using Indexes
• MongoDB slow delete with onDelete: SetNull
• Slow query with many-to-one relationship on MongoDB
• prisma init --with-model
• Fixed version of @opentelemetry/* dependencies
• Usage of deprecated punycode module
• Bug: D1 One-to-Many Relation INSERTs fail with The required connected records were not found. when using indices

Prisma Migrate

• Empty dbgenerated() still breaking for Unsupported() types
• Validation error when shadowDatabaseUrl is identical to url (or directUrl)
• MongoDB Query with 'in' condition will cause COLLSCAN, without leveraging indexes
• "Not Authorised" when directly applying Prisma generated migrations to Cloudflare D1 with PRAGMA foreign_key_check;

Language tools (e.g. VS Code)

• make superior: model generate
• Missing code autocomplete for referential actions with mongodb

Company news

Prisma Changelog

Curious about all things Prisma? Be sure to check out the Prisma Changelog for updates across Prisma's products, including ORM, Accelerate, and Pulse!

Credits

Huge thanks to @​pranayat, @​yubrot, @​skyzh, @​anuraaga, @​gutyerrez, @​avallete, @​ceddy4395, @​Kayoshi-dev for helping!

v5.13.0

Compare Source

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

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

Highlights

omit fields from Prisma Client queries (Preview)

We’re excited to announce Preview support for the omit option within the Prisma Client query options. The highly-requested omit feature now allows you to exclude fields that you don’t want to retrieve from the database on a per-query basis.

By default, when a query returns records, the result includes all scalar fields of the models defined in the Prisma schema. select can be used to return specific fields, while omit can now be used to exclude specific fields. omit lives at the same API level and works on all of the same Prisma Client model queries as select. Note, however, that omit and select are mutually exclusive. In other words, you can’t use both in the same query.

To get started using omit, enable the omitApi Preview feature in your Prisma schema:

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

Be sure to re-generate Prisma Client afterwards:

npx prisma generate

Here is an example of using omit:

// Includes all fields except password
await prisma.user.findMany({
  omit: {
   password: true
  },
})

Here is an example of using omit with include:

// Includes all user fields except user's password and title of user's posts
await prisma.user.findMany({
  omit: {
   password: true
  },
  include: {
    posts: {
      omit: {
        title: true
      },
    },
  },
})

Expand to view the example Prisma schema

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

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

Many users have requested a global implementation of omit. This request will be accommodated in the future. In the meantime, you can follow the issue here.

📣 Share your feedback: omitApi Preview feature

📚 Documentation: omit - Prisma Client API Reference

Fixes and improvements

Prisma Migrate

• Nicer Datamodel Type validation

Prisma Client

• ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using Powershell)

Credits

Huge thanks to @​ospfranco, @​pranayat, @​yubrot, @​skyzh, @​anuraaga, @​yehonatanz, @​arthurfiorette, @​elithrar, @​tockn, @​Kuhave, @​obiwac for helping!

v5.12.1

Compare Source

Today, we are issuing the 5.12.1 patch release to fix two small problems with our new Cloudflare D1 support.

Fixes in Prisma CLI

Windows-only fix for new D1 specific flags for migrate diff and db pull

The flags --from-local-d1 and --to-local-d1 for migrate diff and --local-d1 to db pull we added in 5.12.0 were not working as expected when running on Windows only. This is now fixed.

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

New option for migrate diff: -o or --output

We added a new parameter --output to migrate diff that can be used to provide a filename into which the output of the command will be written. This is particularly useful for Windows users, using PowerShell, as using > to write into a file creates a UTF-16 LE file that can not be read by wrangler d1 migrations apply. Using this new option, this problem can be avoided:

npx prisma migrate diff --script --from-empty --to-schema-datamodel ./prisma/schema.prisma --output ./schema.sql

Related issues:

• ✘ [ERROR] near "��": syntax error at offset 0 when running wrangler d1 migrations apply with Prisma generated migration (on Windows, using PowerShell) #​23702
• [prisma migrate resolve --applied not working on new project, migration ... could not be found.][https://github.com/prisma/prisma/issues/17558](https://togithub.com/prisma/prisma/issues/17558)8)

v5.12.0

Compare Source

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

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

Highlights

Cloudflare D1 (Preview)

This release brings Preview support for Cloudflare D1 with Prisma ORM 🥳

D1 is Cloudflare’s SQLite database that can be used when deploying applications with Cloudflare.

When using Prisma ORM with D1, you can continue to: model your database with Prisma schema language, specify sqlite as your database provider in your Prisma schema, and interact with your database using Prisma Client.

To use Prisma ORM and D1 on Cloudflare Workers or Cloudflare Pages, you need to set sqlite as your database provider and use the @prisma/adapter-d1 database adapter via the driverAdapters Preview feature, released back in version 5.4.0.

Here is an example of sending a query to your D1 database using Prisma Client in your Worker:

// src/index.ts file
import { PrismaClient } from '@​prisma/client'
import { PrismaD1 } from '@​prisma/adapter-d1'

// Add the D1Database to the Env interface
export interface Env {
// This must match the binding name defined in your wrangler.toml configuration
  DB: D1Database
}

export default {
  async fetch(
    request: Request,
    env: Env,
    ctx: ExecutionContext
  ): Promise<Response> {
    // Make sure the database name matches the binding name in wrangler.toml and Env interface
    const adapter = new PrismaD1(env.DB)
    // Instantiate PrismaClient using the PrismaD1 driver adapter
    const prisma = new PrismaClient({ adapter })

    const users = await prisma.user.findMany()
    const result = JSON.stringify(users)
    return new Response(result)
  },
}

📚 Documentation: Deploying a Cloudflare worker with D1 and Prisma ORM

✍️ Blog post: Build Applications at the Edge with Prisma ORM & Cloudflare D1 (Preview)

📣 Share your feedback: D1 Driver Adapter

🚀 Example project: Deploy a Cloudflare Worker with D1

createMany() for SQLite

Bringing support for createMany() in SQLite has been a long-awaited and highly requested feature ⭐

createMany() is a method on Prisma Client, released back in version 2.16.0, that lets you insert multiple records into your database at once. This can be really useful when seeding your database or inserting bulk data.

Here is an example of using createMany() to create new users:

const users = await prisma.user.createMany({
  data: [
    { name: 'Sonali', email: '[email protected]' },
    { name: 'Alex', email: '[email protected]' },
    { name: 'Yewande', email: '[email protected]' },
    { name: 'Angelina', email: '[email protected]' },
  ],
})

Before this release, if you wanted to perform bulk inserts with SQLite, you would have most likely used $queryRawUnsafe to execute raw SQL queries. But now you don’t have to go through all that trouble 🙂

With SQLite, createMany() works exactly the same way from an API standpoint as it does with other databases except it does not support the skipDuplicates option. At the behavior level, SQLite will split createMany() entries into multiple INSERT queries when the model in your schema contains fields with attributes like @default(dbgenerated()) or @default(autoincrement()) and when the fields are not consistently provided with values across the entries.

📚Documentation: createMany() - Prisma Client API Reference

Fixes and Improvements

Prisma Client

• N+1 Issue with Decimal data type and combining queries (batching)
• Batched findUnique() error out when the field is of Boolean type
• relationJoins MySQL converts nested Decimal to float
• Unexpected query leading to querying full table when using batched findUnique()
• node-postgres (pg) errors with misleading P2010 PrismaClientKnownRequestError when using @prisma/adapter-pg with SSL (?sslmode=require)
• D1 DateTime type does not work

Credits

Huge thanks to @​yubrot, @​skyzh, @​anuraaga, @​onichandame, @​LucianBuzzo, @​RobertCraigie, @​arthurfiorette, @​elithrar for helping!

KengoTODA/actions-setup-docker-compose (KengoTODA/actions-setup-docker-compose)

v1.2.2

Compare Source

Bug Fixes

• deps: update dependency @​octokit/action to v6.1.0 (d6b647d)

postcss/autoprefixer (autoprefixer)

v10.4.19

Compare Source

• Removed end value has mixed support, consider using flex-end warning
  since end/start now have good support.

lukeed/clsx (clsx)

v2.1.1

Compare Source

Patches

• (types) Include bigint in ClassValue type: (#​96): 3d960ab
  Accommodates recent @types/react changes to ReactNode.
  Thank you @​ViliamKopecky~!

Chores

• Add licenses.dev badge: 684509c
  This service recursively analyzes entire dependency graphs to ensure that a package (or your project) is using permissive licenses. For example, here's a results table for polka@next and a larger astro example.

---

Full Changelog: lukeed/clsx@v2.1.0...v2.1.1

cypress-io/cypress (cypress)

v13.10.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-10-0

v13.9.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-9-0

v13.8.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-8-1

v13.8.0

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-8-0

v13.7.3

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-7-3

v13.7.2

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-7-2

v13.7.1

Compare Source

Changelog: https://docs.cypress.io/guides/references/changelog#13-7-1

iamkun/dayjs (dayjs)

v1.11.11

Compare Source

Bug Fixes

• day of week type literal (#​2630) (f68d73e)
• improve locale "zh-hk" format and meridiem (#​2419) (a947a51)
• Update 'da' locale to match correct first week of year (#​2592) (44b0936)
• update locale Bulgarian monthsShort Jan (#​2538) (f0c9a41)

vercel/next.js (eslint-config-next)

v14.2.3

Compare Source

v14.2.2

Compare Source

v14.2.1

Compare Source

v14.2.0

Compare Source

v14.1.4

Compare Source

cypress-io/eslint-plugin-cypress (eslint-plugin-cypress)

v2.15.2

Compare Source

jsx-eslint/eslint-plugin-react (eslint-plugin-react)

v7.34.2

Compare Source

Fixed

• [boolean-prop-naming][boolean-prop-naming]: avoid a crash with a non-TSTypeReference type (#​3718 @​developer-bandi)
• [jsx-no-leaked-render][jsx-no-leaked-render]: invalid report if left side is boolean (#​3746 @​akulsr0)
• [jsx-closing-bracket-location][jsx-closing-bracket-location]: message shows {{details}} when there are no details (#​3759 @​mdjermanovic)
• [no-invalid-html-attribute][no-invalid-html-attribute]: ensure error messages are correct (#​3759 @​mdjermanovic, @​ljharb)

Changed

• [Refactor] create various eslint utils to fix eslint deprecations (#​3759 @​mdjermanovic, @​ljharb)

facebook/react (eslint-plugin-react-hooks)

v4.6.2

Compare Source

v4.6.1

Compare Source

SonarSource/eslint-plugin-sonarjs (eslint-plugin-sonarjs)

v0.25.1

Compare Source

What's Changed

• Resolve issue #​456 - @​typescript-eslint/utils dependency is missing by @​ericmorand-sonarsource in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/457
• Bump the project manifest version to 0.25.1 by @​ericmorand-sonarsource in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/458

New Contributors

• @​ericmorand-sonarsource made their first contribution in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/457

Full Changelog: SonarSource/eslint-plugin-sonarjs@0.25.0...0.25.1

v0.25.0

Compare Source

What's Changed

• Prepare for next development iteration by @​yassin-kammoun-sonarsource in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/446
• Fix FP 3699 (no-use-of-empty-return-values) to handle ambient functions by @​zglicz in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/451
• Make no-unused-collection not trigger if writing to elements of said collection by @​zglicz in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/452
• Replace devDependency @typescript-eslint/experimental-utils with @typescript-eslint/utils by @​yassin-kammoun-sonarsource in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/453

New Contributors

• @​zglicz made their first contribution in https://github.com/SonarSource/eslint-plugin-sonarjs/pull/451

Full Changelog: SonarSource/eslint-plugin-sonarjs@0.24.0...0.25.0

vercel/geist-font (geist)

v1.3.0

Compare Source

Changelog

• Improved drawing quality of base letters, numbers, diacritics.
• Heaviest master x-height raised for better optical compensation.
• Extended kerning to accented letters.
• Improved drawing quality of base glyphs
• Fixed vertical caron design
• Added missing box drawing character https://github.com/vercel/geist-font/issues/64
• Set Regular master as default instance https://github.com/vercel/geist-font/issues/68
• Fixed size of ordfemenine and ordmasculine
• Removed unnecesary full width punctuation
• Fixed width of small figures
• Improved set up for auto hinting
• Fixed Vertical metrics to avoid clipping on Windows
• Small drawing fixes in other glyphs

pilcrowOnPaper/lucia (lucia)

v3.2.0

Minor changes

• #​1548 by @​pilcrowOnPaper : Add generateIdFromEntropySize()

Patch changes

• #​1546 by @​pilcrowOnPaper : Fix options.sessionCookie parameter type in Lucia

• #​1548 by @​pilcrowOnPaper : Optimize session ID generation

lucide-icons/lucide (lucide-react)

v0.381.0: New icons 0.381.0

Compare Source

New icons 🎨

• lectern (#​2171) by @​karsa-mistmere

v0.380.0: New icons 0.380.0

Compare Source

New icons 🎨

• section (#​2172) by [@​karsa-mistmere

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.