How to use @prisma/nextjs-monorepo-workaround-plugin with Turbo Pack ( next --turbo )

[davecarlson]

Question

currently, to use the plugin we do :

webpack: (config, { isServer }) => {
    if (isServer) {
      config.plugins = [...config.plugins, prismaPlugin];
    }

    return config;
  }

however, this throws issues if you are using turbopack (next --turbo):

⚠ Webpack is configured while Turbopack is not, which may cause problems.
 ⚠ See instructions if you need to configure Turbopack:
https://nextjs.org/docs/app/api-reference/next-config-js/turbo

How to reproduce (optional)

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

// Add your schema.prisma

// Add any relevant Prisma Client queries here

• OS:

• Database:

• Node.js version:

• Run prisma -v to see your Prisma version and paste it

[ludralph]

Hi @davecarlson 👋

Thank you for raising this question.

The @prisma/nextjs-monorepo-workaround-plugin was a solution for Next.js monorepo setups. It might not be the best approach with Turbo Pack. The reason is Turbo Pack has built-in support for Prisma within a monorepo structure. This eliminates the need for an additional workaround plugin. Did you take a look at this section of the Turbo Repo documentation on how to setup Prisma with Turbo repo?

[davecarlson]

We are already on a turborepo ( have been over a year). ( and had used that guide).

Please note, its absolutely fine on normal build, just not the new --turbo build option ( turbo pack is separate to turbo repo )