Prisma: Issue properly keeping the prisma2 @prisma/client out of the client side bundle in Next.js

Created on 28 Feb 2020 · 3Comments · Source: prisma/prisma

I'm just quoting's @flybayer's message from the Prisma Slack turning it into a public GitHub issue

We’re currently having an issue properly keeping the prisma2 @prisma/client out of the client side bundle in Next.js, (using it from getServerSideProps).

The Blitz core and example code on the canary branch works properly in production, but not in development.

Here’s the code where @prisma/client is required from blitz core

This blog post shows different ways to do this, but none of them are working when an npm package is requiring @prisma/client.

This comment describes our current issue.

This PR shows the hack we have to use right now to get it working in development

bu0-needs-info kinbug

Source

nikolasburk

Most helpful comment

Good news: I found a good solution for this!

yarn install null-loader
Add the following to next.config.js

module.exports = {
  webpack(config, { isServer }) {
    if (!isServer) {
      // Ensure prisma client is not included in the client bundle
      config.module.rules.push({
        test: /@prisma\/client/,
        use: "null-loader",
      })
    }
    return config
  },
}

flybayer on 3 Mar 2020

🚀2 🎉2

All 3 comments

Good news: I found a good solution for this!

yarn install null-loader
Add the following to next.config.js

module.exports = {
  webpack(config, { isServer }) {
    if (!isServer) {
      // Ensure prisma client is not included in the client bundle
      config.module.rules.push({
        test: /@prisma\/client/,
        use: "null-loader",
      })
    }
    return config
  },
}

flybayer on 3 Mar 2020

🚀2 🎉2

Hey @flybayer,

Now that Next.js 9.3 is out, can you please confirm that you are able to still reproduce this.

If yes, can you share a minimal reproduction in a Git repository? If you can also configure that reproduction with webpack bundle analyzer, that would be super nice.