prisma: Generating client to custom location with Next.js is broken

Just tried it out - I can confirm that this is fixed in the latest version. Let me know if you face any further issues @colinhacks and @flybayer 🙂

This will be fixed in https://github.com/vercel/vercel/pull/5455

Perhaps that config could be added to https://github.com/prisma-labs/next-prisma-plugin?

EDIT: This breaks dev mode 😕 https://github.com/prisma/prisma/issues/2195#issuecomment-717576013

I solved this issue for myself by doing a couple things:

1. overriding the node.__dirname Webpack setting inside next.config.js so it’s true in development and false in production.
2. Copying the binary into the appropriate folders of .next/serverless using copy-webpack-plugin

// node.config.js

const CopyWebpackPlugin = require('copy-webpack-plugin'); // npm install copy-webpack-plugin
const path = require('path');

module.exports = {
  // stuff here
  webpack: (config, { buildId, dev, isServer, defaultLoaders, webpack }) => {
    
    // set to `dev`
    config.node.__dirname = dev;
    
    // copy binary into the appropriate locations within `.next/serverless`
    config.plugins.push(
      new CopyWebpackPlugin({
        patterns: [
          {

            // the custom location the binary is generated to
            from: path.join(
              __dirname,
              'path/to/binary/query-engine*', // glob pattern that matches all query-engines
            ),

            to: path.join(__dirname, '.next/serverless/pages/api'),
          },
        ],
      }),
    );

    
    return config;
  },
};

This solution was first proposed here.

Related issues:

• https://github.com/prisma/prisma/issues/2303
• https://github.com/prisma/prisma-client-js/issues/616
• https://github.com/prisma/prisma/issues/2195