⬆️ Bump @prisma/client from 2.30.3 to 4.1.1

[dependabot]

Bumps @prisma/client from 2.30.3 to 4.1.1.

Release notes

Sourced from @​prisma/client's releases.

4.1.1

Today, we are issuing the 4.1.1 patch release.

Fix in Prisma Studio

• Fixed a regression in Prisma Studio introduced in 4.1.0, that caused horizontal scrolling to not always work

4.1.0

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

Upgrading to Prisma 4

In case you missed it, we held a livestream last week and walked through issues you may run into while upgrading to Prisma 4 and how to fix them!

Major improvements

Ordering by nulls first and last support (Preview)

In this release, we're adding support for choosing how to sort null values in a query.

To get started, enable the orderByNulls Preview feature flag in your Prisma schema:

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

Next, run prisma generate to re-generate Prisma Client. You will now have new fields you can now use to order null values:

await prisma.post.findMany({
  orderBy: {
    updatedAt: { 
      sort: 'asc',
      nulls: 'last'
    },
  },
})

Learn more in our documentation and don't hesitate to share your feedback in this issue.

Fixed memory leaks and CPU usage in Prisma Client

In this release, we've fixed the following issues experienced when setting up and tearing down Prisma Client while running tests:

1. Prisma Client now correctly releases memory on Prisma Client instances that are no longer being used. Learn more in this GitHub issue
2. Reduced CPU usage spikes when disconnecting Prisma Client instances while using Prisma Client. You can learn more in this GitHub issue

... (truncated)

Commits

• 5a69028 test: add orderby test (#14376)
• b2e754f chore(deps): update engines to 4.1.0-48.8d8414deb360336e4698a65aa45a1fbaf1ce1...
• 118cae0 chore: remove maintainers from package.json (#14123)
• 77c9e3d test: Update tracing to the latest changes in test setup (#14331)
• f0ef3fb fix: Allow engine to be GCed correctly (#14174)
• 7b4b344 chore(deps): update engines to 4.1.0-46.ae5f7292ee190618fb240e81444c0b15a5e96...
• e4ba030 feat(client): Consolidating Tracing (#13980)
• 0c573b3 chore(deps): update engines to 4.1.0-45.35a6cc3c23c9f0c0cbab0b811e9a204577408...
• 9dc5c64 test: Port composites-mongo test to new setup (#13839)
• 7a2eb91 chore(deps): update engines to 4.1.0-44.d006f517279f66d50eb3cf34f3382605c055c...
• Additional commits viewable 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 ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #26.