Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 400-nextjs-prisma-client-dev-practices.mdx #5384

Merged
merged 2 commits into from
Oct 24, 2023
Merged

Update 400-nextjs-prisma-client-dev-practices.mdx #5384

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c386055
Update 400-nextjs-prisma-client-dev-practices.mdx
zhandosm Oct 17, 2023
3a71058
Update content/300-guides/500-other/880-troubleshooting-orm/100-help-…
ruheni Oct 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...roubleshooting-orm/100-help-articles/400-nextjs-prisma-client-dev-practices.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ In development, the command `next dev` clears Node.js cache on run. This in turn

The solution in this case is to instantiate a single instance `PrismaClient` and save it on the [`globalThis`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/globalThis) object. Then we keep a check to only instantiate `PrismaClient` if it's not on the `globalThis` object otherwise use the same instance again if already present to prevent instantiating extra `PrismaClient` instances.

```ts file=./db
```ts file=db.ts
import { PrismaClient } from '@prisma/client'

const prismaClientSingleton = () => {
Expand Down
Loading