Andy Young

@LucaNerlich updated my comment above to demonstrate how I got my relative imports working also.

> Just a note, if you import a .scss file from in a package that you don't control which imports via `~` (in my case a third party package uses...

Working great - with Data Proxy (after applying temporary workaround for https://github.com/prisma/prisma/issues/18549) Relatively modest `schema.prisma`: ~1k lines (34 models, 14 enums) Before: - time to execute `new PrismaClient()`: ~60-70ms -...

> no way to leak some context to another query [that does not set its own context] AFAIK yes - the only way to achieve this (assuming connection pooling) is...

Incredible! Thanks @remagpie Tweaked to work with esm and ts-node using: ```yaml runtime: name: nodejs options: typescript: false nodeargs: "--experimental-specifier-resolution=node --loader ts-node/esm" ```

> I specifically added `@neondatabase/serverless` to transpiledPackages in the nextjs.config.js. > > My usecase is that we export prisma in a monorepo workspace (in a different project) that is transpiled...

> We have a internal package (in our codebase) that exports a CMS which uses prisma. That internal package is used in the nextjs project so that internal package needs...

All I can say is I'm also using turborepo with nextjs + internal packages in a monorepo + Neon driverAdapter and not getting any error - so I assume we're...

This patch fixes for me. Specifically: prevents the error `Error: The edge runtime does not support Node.js 'crypto' module.` when using `pg` under the Next.js Edge runtime locally. `pg+8.11.5.patch`: ```patch...

@brianc here you go - reproduction for pages router: https://github.com/andyjy/mre-pg-nextjs-edge