next dev --turbo errors when turborepo internal package imports node native module about next.js HOT 2 CLOSED

The issue seems to be unrelated to Turbopack/Turborepo.

https://github.com/dbrxnds/turbo-crypto-repro/blob/63f82a9856925bdbe35a6c4d1c7bc86bce99c5a1/packages/ui/src/button.tsx#L4

here, you are importing Node.js internals in a client component, which is not allowed, as it will run in the browser as well.

If you only need randomUUID(), you can just call crypto.randomUUID() directly without any Node.js import, as it's available in all major browsers already.

In our own application this same issue occurs for Prisma imports that come from our mysql internal workspace. So I'm not sure if it's necessarily related to node native modules, but this allowed for the easiest/most minimal reproduction.

I would check the same, make sure you aren't using Prisma in a client component directly. Without seeing the code it's hard to make further assumptions though.

from next.js.

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

from next.js.