ok when i check it's call seq, testSingleton called twice.

why it called again after rendered? 🤔

(0 => 1): testSingleton => (2): layout => (0 => 1): testSingleton

how are you doing the test?

just with
next dev + app dir

and are those just froma single request or multiple requests

just for every request, testSingleton sequence called twice

can i show you how i set up my singleton?

sure! i'll test again with that method

this log for single request

I called it everywhere on the page so it should show up more than 2, but here it only show up once or twice

ideally every request should show up once only

but it might be inconsistencies with dev server. one should try in prod

[source](https://www.prisma.io/docs/guides/other/troubleshooting-orm/help-articles/nextjs-prisma-client-dev-practices#solution)

Is it a correct for notion client to be created on every request?

Im deploying it on Vercel so it has to be stateless. yes

if you deploy it on non-serverless architecture, i believe you could just make global exports normally lol

i.e nothing can persists between requests

even is it with non-serverless?

Vercel is serverless so no, that doesn't apply

In prod it works as expected.
In dev, keep got "The server is running out of memory, restarting to free up memory", it's why i dig this stuff.
maybe this is causing a memory leak in the dev. (Importing twice in rsc?)
I will debug heap and check second import is disposed. if not i will write a gh issue for it.
thank you!

No problem!

do you know why it behaves like that?
I'd like to know if this is the intended implementation.