fix: all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@aws-sdk/client-ses (source)	3.540.0 -> 3.569.0
@fontsource/fira-mono (source)	5.0.12 -> 5.0.13
@playwright/test (source)	1.42.1 -> 1.43.1
@prisma/client (source)	5.11.0 -> 5.13.0
@sveltejs/kit (source)	2.5.5 -> 2.5.7
@types/lodash (source)	4.14.202 -> 4.17.1
@typescript-eslint/eslint-plugin (source)	7.4.0 -> 7.8.0
@typescript-eslint/parser (source)	7.4.0 -> 7.8.0
eslint-plugin-svelte (source)	2.35.1 -> 2.38.0
nanoid	5.0.6 -> 5.0.7
prettier-plugin-svelte	3.2.2 -> 3.2.3
prettier-plugin-tailwindcss	0.5.13 -> 0.5.14
prisma (source)	5.11.0 -> 5.13.0
svelte (source)	4.2.12 -> 4.2.15
svelte-check	3.6.8 -> 3.7.1
tailwind-merge	2.2.2 -> 2.3.0
typescript (source)	5.4.3 -> 5.4.5
vite (source)	5.2.7 -> 5.2.11
vitest (source)	1.4.0 -> 1.6.0
zod (source)	3.22.4 -> 3.23.6

---

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-ses)

v3.569.0

Compare Source

Bug Fixes

• clients: add deps required by default credential providers (#​6055) (bfa8626)

v3.568.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.567.0

Compare Source

Features

• end support for Node.js 14.x (#​6034) (d196411)

v3.565.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.564.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.563.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.556.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.554.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.552.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

v3.549.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-ses

fontsource/font-files (@​fontsource/fira-mono)

v5.0.13

Compare Source

microsoft/playwright (@​playwright/test)

v1.43.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/30300 - [REGRESSION]: UI mode restarts if keep storage statehttps://github.com/microsoft/playwright/issues/303399 - [REGRESSION]: Brand new install of playwright, unable to run chromium with show browser using vscode

Browser Versions

• Chromium 124.0.6367.29
• Mozilla Firefox 124.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 123
• Microsoft Edge 123

v1.43.0

Compare Source

New APIs

• Method browserContext.clearCookies() now supports filters to remove only some cookies.

  // Clear all cookies.
  await context.clearCookies();
  // New: clear cookies with a particular name.
  await context.clearCookies({ name: 'session-id' });
  // New: clear cookies for a particular domain.
  await context.clearCookies({ domain: 'my-origin.com' });

• New mode retain-on-first-failure for testOptions.trace. In this mode, trace is recorded for the first run of each test, but not for retires. When test run fails, the trace file is retained, otherwise it is removed.

  import { defineConfig } from '@​playwright/test';
  
  export default defineConfig({
    use: {
      trace: 'retain-on-first-failure',
    },
  });

• New property testInfo.tags exposes test tags during test execution.

  test('example', async ({ page }) => {
    console.log(test.info().tags);
  });

• New method locator.contentFrame() converts a Locator object to a FrameLocator. This can be useful when you have a Locator object obtained somewhere, and later on would like to interact with the content inside the frame.

  const locator = page.locator('iframe[name="embedded"]');
  // ...
  const frameLocator = locator.contentFrame();
  await frameLocator.getByRole('button').click();

• New method frameLocator.owner() converts a FrameLocator object to a Locator. This can be useful when you have a FrameLocator object obtained somewhere, and later on would like to interact with the iframe element.

  const frameLocator = page.frameLocator('iframe[name="embedded"]');
  // ...
  const locator = frameLocator.owner();
  await expect(locator).toBeVisible();

UI Mode Updates

• See tags in the test list.
• Filter by tags by typing @fast or clicking on the tag itself.
• New shortcuts:
  • F5 to run tests.
  • Shift F5 to stop running tests.
  • Ctrl ` to toggle test output.

Browser Versions

• Chromium 124.0.6367.29
• Mozilla Firefox 124.0
• WebKit 17.4

This version was also tested against the following stable channels:

• Google Chrome 123
• Microsoft Edge 123

prisma/prisma (@​prisma/client)

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: 'sonali@prisma.io' },
    { name: 'Alex', email: 'alex@prisma.io' },
    { name: 'Yewande', email: 'yewande@prisma.io' },
    { name: 'Angelina', email: 'angelina@prisma.io' },
  ],
})

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!

sveltejs/kit (@​sveltejs/kit)

v2.5.7

Compare Source

Patch Changes

• chore(deps): update devalue to v5 ignore non-enumerable symbols during serialization (#​12141)

v2.5.6

Compare Source

Patch Changes

• fix: avoid incorrectly un- and re-escaping cookies collected during a server-side fetch (#​11904)

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v7.8.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-unsafe-argument] handle tagged templates

• eslint-plugin: [prefer-optional-chain] suggests optional chaining during strict null equality check

• eslint-plugin: [consistent-type-assertions] handle tagged templates

• eslint-plugin: [no-unsafe-return] handle union types

• eslint-plugin: [no-unused-vars] clear error report range

❤️ Thank You

• auvred
• Josh Goldberg ✨
• jsfm01
• Kim Sang Du
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

🩹 Fixes

• eslint-plugin: [no-unsafe-assignment] handle shorthand property assignment

• eslint-plugin: [explicit-function-return-type] fix checking wrong ancestor's return type

• eslint-plugin: [prefer-optional-chain] only look at left operand for requireNullish

• eslint-plugin: [no-for-in-array] refine report location

• eslint-plugin: [no-unnecessary-type-assertion] allow non-null assertion for void type

❤️ Thank You

• Abraham Guo
• Kirk Waiblinger
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

🚀 Features

• eslint-plugin: replace no-new-symbol with no-new-native-nonconstructor

❤️ Thank You

• Dave
• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

v7.6.0

Compare Source

🚀 Features

• bump npm dependency ranges

❤️ Thank You

• Abraham Guo
• auvred
• Brad Zacher

You can read about our versioning strategy and releases on our website.

v7.5.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression

• eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v7.8.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.1

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.7.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v7.6.0

Compare Source

🚀 Features

• bump npm dependency ranges

❤️ Thank You

• Abraham Guo
• auvred
• Brad Zacher

You can read about our versioning strategy and releases on our website.

v7.5.0

Compare Source

🩹 Fixes

• parser: disallow errorOnTypeScriptSyntacticAndSemanticIssues

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v2.38.0

Compare Source

Minor Changes

• #​741 33626a3 Thanks @​baseballyama! - Use the latest Svelte 5

v2.37.0

Compare Source

Minor Changes

• #​735 33f0de2 Thanks @​xiBread! - feat: add rule types

v2.36.0

Compare Source

Minor Changes

• Add experimental support for Svelte v5
  • #​622 470ef6c Thanks @​ota-meshi! - feat: add support for {@​snippet}and {@​render} in indent rule
  • #​620 1097107 Thanks @​ota-meshi! - feat: (experimental) partial support for Svelte v5
  • #​624 7df5b6f Thanks @​ota-meshi! - feat: add support for {@​snippet} and {@​render} in mustache-spacing rule
  • Update parser and svelte(v5)
    • #​657 b159b46 Thanks @​ota-meshi! - feat: update svelte to v5.0.0-next.33
    • #​704 af2ccf9 Thanks @​ota-meshi! - Update svelte-eslint-parser
    • #​693 b11ff34 Thanks @​ota-meshi! - fix: update dependencies & some fixes
    • #​628 85fc8f4 Thanks @​ota-meshi! - fix: update parser and fix some tests
    • #​696 d4303f5 Thanks @​ota-meshi! - fix: update svelte-eslint-parser
    • #​635 ec3f1cf Thanks @​ota-meshi! - feat: update svelte to v5.0.0-next.16
    • #​687 2943021 Thanks @​ota-meshi! - feat: update parser
• Support for ESLint v9
  • #​673 b72b97b Thanks @​ota-meshi! - feat: add support for eslint v9
  • #​708 d597a69 Thanks @​ota-meshi! - feat: add support for flat config
    • #​719 eaf5e6a Thanks @​ota-meshi! - fix: suppress comment not working in flat config.
    • #​711 aaba61f Thanks @​ota-meshi! - fix: flat config would cause an error with non-svelte files
• #​690 e84397d Thanks @​sdarnell! - Added prefer option to prefer-class-directive rule ('always' or 'empty'). The default is now 'empty' which is a slight relaxation of the rule.
• #​679 4e6c681 Thanks @​marekdedic! - feat: added the no-goto-without-base rule

Patch Changes

• #​694 73d6fd8 Thanks @​ota-meshi! - fix: style report location
• #​670 6121a56 Thanks @​renovate! - fix(deps): update dependency eslint-compat-utils to ^0.3.0

ai/nanoid (nanoid)

v5.0.7

Compare Source

• Fixed Parcel support (by @​WilhelmYakunin).

sveltejs/prettier-plugin-svelte (prettier-plugin-svelte)

v3.2.3

Compare Source

• (fix) don't force-self-close <slot> tags

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.5.14

Compare Source

Fixed

• Fix detection of v4 projects on Windows (#​265)

sveltejs/svelte (svelte)

v4.2.15

Compare Source

Patch Changes

• support attribute selector inside :global() (#​11135)

v4.2.14

Compare Source

Patch Changes

• fix parsing camelcase container query name (#​11131)

v4.2.13

Compare Source

Patch Changes

• fix: applying :global for +,~ sibling combinator when slots are present (#​9282)

sveltejs/language-tools (svelte-check)

v3.7.1

Compare Source

• fix: rework bindable types strategy (#​2361)

v3.7.0

Compare Source

• feat: mark only properties as bindable that were declared using $bindable() in Svelte 5 runes mode (#​2336)
• chore: better Svelte 5 interop (#​2336)
• fix: preserve event attribute casing in Svelte 5 (#​2347)
• fix: handle #await inside #snippet (#​2348)
• fix: better bind:group transformation (#​2349)
• fix: handle boolean css var (#​2350)

v3.6.9

Compare Source

• fix: ensure type widening for bind:group
• perf: improve perf in deleteUnresolvedResolutionsFromCache (#​2320)
• fix: adjust for moved compiler file in Svelte 5 (#​2327)

dcastil/tailwind-merge (tailwind-merge)

v2.3.0

Compare Source

New Features

• Add support for mix-blend-plus-darker utility by @​dcastil in https://github.com/dcastil/tailwind-merge/pull/403
• Added support for bigint in ClassNameValue type by @​LarsArtmann in https://github.com/dcastil/tailwind-merge/pull/402

Documentation

• Add tailwind-merge-go to similar packages in docs by @​Oudwins in https://github.com/dcastil/tailwind-merge/pull/396

Full Changelog: dcastil/tailwind-merge@v2.2.2...v2.3.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy and @​jamesreaco for sponsoring tailwind-merge! ❤️

Microsoft/TypeScript (typescript)

v5.4.5: TypeScript 5.4.5

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).
• fixed issues query for Typescript 5.4.5 (Stable).

Downloads are available on:

• NuGet package

v5.4.4: TypeScript 5.4.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).

Downloads are available on:

• NuGet package

vite

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone Australia/Melbourne, 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 has been generated by Mend Renovate. View repository job log here.