Bump the misc group with 5 updates

[dependabot]

Bumps the misc group with 5 updates:

Package	From	To
@prisma/client	5.18.0	5.19.0
@prisma/instrumentation	5.18.0	5.19.0
next	14.2.6	14.2.7
@types/react	18.3.4	18.3.5
prisma	5.18.0	5.19.0

Updates @prisma/client from 5.18.0 to 5.19.0

Release notes

Sourced from @​prisma/client's releases.

5.19.0

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

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

Highlights

Introducing TypedSQL

TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.

To get started with TypedSQL:

1. Make sure that you have the latest version of prisma and @prisma/client installed:

   npm install -D prisma@latest
   npm install @prisma/client@latest
   

2. Enable the typedSql Preview feature in your Prisma Schema.

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

3. Create a sql subdirectory of your prisma directory.

   mkdir -p prisma/sql
   

4. You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:

   SELECT u.id, u.name, COUNT(p.id) as "postCount"
   FROM "User" u
   LEFT JOIN "Post" p ON u.id = p."authorId"
   GROUP BY u.id, u.name

5. Import your SQL query into your code with the @prisma/client/sql import:

      import { PrismaClient } from '@prisma/client'
      import { getUsersWithPosts } from '@prisma/client/sql'

... (truncated)

Commits

• 0f63437 chore(deps): update engines to 5.19.0-31.5fe21811a6ba0b952a3bc71400666511fe3b...
• a411e43 chore(deps): update engines to 5.19.0-30.de1356e7b79f44aaa2d308a544c32a4d2951...
• 1ff458a chore(deps): update engines to 5.19.0-27.0bc306ebdcdb88c93b6fd25d43855afc7e4f...
• 8957496 feat(client): Typed SQL (#24907)
• 2afa20b chore(deps): update engines to 5.19.0-26.8a3982b39f6dc8065ba99a0d212b3e18a5cd...
• f3856a9 chore(deps): update devdependencies patch (non-major) (#24813)
• 2d27e8c chore(deps): update engines to 5.19.0-23.c356d1b4064663e128504e183e2b0cbe5fcd...
• 78cbbfd chore(deps): update engines to 5.19.0-19.cb8fbf23062d1b8788a70d0d0cd3d2e0bd6e...
• b28fa63 chore(deps): update engines to 5.19.0-12.ae18f9165678fc6c7b7b107340ca0435be43...
• 3b585cc chore(deps): update engines to 5.19.0-8.44f753d2ce0008a24ce36e34aff65a5afe266...
• Additional commits viewable in compare view

Updates @prisma/instrumentation from 5.18.0 to 5.19.0

Release notes

Sourced from @​prisma/instrumentation's releases.

5.19.0

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

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

Highlights

Introducing TypedSQL

TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.

To get started with TypedSQL:

1. Make sure that you have the latest version of prisma and @prisma/client installed:

   npm install -D prisma@latest
   npm install @prisma/client@latest
   

2. Enable the typedSql Preview feature in your Prisma Schema.

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

3. Create a sql subdirectory of your prisma directory.

   mkdir -p prisma/sql
   

4. You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:

   SELECT u.id, u.name, COUNT(p.id) as "postCount"
   FROM "User" u
   LEFT JOIN "Post" p ON u.id = p."authorId"
   GROUP BY u.id, u.name

5. Import your SQL query into your code with the @prisma/client/sql import:

      import { PrismaClient } from '@prisma/client'
      import { getUsersWithPosts } from '@prisma/client/sql'

... (truncated)

Commits

• See full diff in compare view

Updates next from 14.2.6 to 14.2.7

Release notes

Sourced from next's releases.

v14.2.7

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• Revert "chore: externalize undici for bundling" (#65727)
• Refactor internal routing headers to use request meta (#66987)
• fix(next): add cross origin in react dom preload (#67423)
• build: upgrade edge-runtime (#67565)
• GTM dataLayer parameter should take an object, not an array of strings (#66339)
• fix: properly patch lockfile against swc bindings (#66515)
• Add deployment id header for rsc payload if present (#67255)
• Update font data (#68639)
• fix i18n data pathname resolving (#68947)
• pages router: ensure x-middleware-cache is respected (#67734)
• Fix bad modRequest in flight entry manifest #68888
• Reject next image urls in image optimizer #68628
• Fix hmr assetPrefix escaping and reuse logic from other files #67983

Credits

Huge thanks to @​kjugi, @​huozhi, @​ztanner, @​SukkaW, @​marlier, @​Kikobeats, @​syi0808, @​ijjk, and @​samcx for helping!

Commits

• a1c3a03 v14.2.7
• d46ab2c Fix hmr assetPrefix escaping and reuse logic from other files (#67983)
• d11cbc9 Reject next image urls in image optimizer (#68628)
• 575385e Fix bad modRequest in flight entry manifest (#68888)
• 9ecf2e8 update turbopack build manifest
• 325dc4b pages router: ensure x-middleware-cache is respected (#67734)
• d3021b6 update playwright interface
• 5e6f511 fix i18n data pathname resolving (#68947)
• dd32e0f Update font data (#68639)
• 2f7fa98 Add deployment id header for rsc payload if present (#67255)
• Additional commits viewable in compare view

Updates @types/react from 18.3.4 to 18.3.5

Commits

• See full diff in compare view

Updates prisma from 5.18.0 to 5.19.0

Release notes

Sourced from prisma's releases.

5.19.0

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

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

Highlights

Introducing TypedSQL

TypedSQL is a brand new way to interact with your database from Prisma Client. After enabling the typedSql Preview feature, you’re able to write SQL queries in a new sql subdirectory of your prisma directory. These queries are then checked by Prisma during using the new --sql flag of prisma generate and added to your client for use in your code.

To get started with TypedSQL:

1. Make sure that you have the latest version of prisma and @prisma/client installed:

   npm install -D prisma@latest
   npm install @prisma/client@latest
   

2. Enable the typedSql Preview feature in your Prisma Schema.

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

3. Create a sql subdirectory of your prisma directory.

   mkdir -p prisma/sql
   

4. You can now add .sql files to the sql directory! Each file can contain one sql query and the name must be a valid JS identifier. For this example, say you had the file getUsersWithPosts.sql with the following contents:

   SELECT u.id, u.name, COUNT(p.id) as "postCount"
   FROM "User" u
   LEFT JOIN "Post" p ON u.id = p."authorId"
   GROUP BY u.id, u.name

5. Import your SQL query into your code with the @prisma/client/sql import:

      import { PrismaClient } from '@prisma/client'
      import { getUsersWithPosts } from '@prisma/client/sql'

... (truncated)

Commits

• 8957496 feat(client): Typed SQL (#24907)
• f3856a9 chore(deps): update devdependencies patch (non-major) (#24813)
• ce552f3 feat(cli): remove Optimize specific login in Platform CLI (#25036)
• 26c8d91 feat(cli): Chokidar-based watch (#24983)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions