prisma: Bundling fails on 2.21.0

With webpack 5, simply adding '_http_common' to an array in the externals build option wasn’t enough for me, I had to specify it this way:

{
  // ...
  externals: {
    "_http_common": "commonjs2 _http_common",
  }
}

In your webpack.config.js, add externals: ['_http_common', 'encoding'],

I can confirm that "@prisma/client": "^3.12.0-dev.28" works. Thanks @millsp !

I have a similar issue with @m-abdelwahab Im using serverless-bundle which uses webpack it was trying to find a module to bundle I needed to ignore the package _http_common for bundling so it work.

@millsp Any recommendations of a workaround in the meantime that does not include simply cutting out the dependency?

_http_common is a private module built into node js itself(https://github.com/nodejs/node/blob/master/lib/_http_common.js), just like fs or util. It is not a publicly documented API. It was used by undici to improve http parsing performance but looks like they no longer need it in the latest release candidate version. undici is maintained by Node JS folks so they know about this undocumented private module pretty well. So that is why you don’t need to bundle it as it is built into the runtime.

Hey everyone, this has been fixed in @prisma/client@dev if you want to give it a try. Please let us know if you find anything unexpected. Thanks.

(cc @prescience-data @ra-kesh @trivigy)

@mubaidr It is for next js. Ignore it if you are not using next js.

We are waiting for undici to release v4, in the meantime you could mark their internal dependency as external with --external:_http_common.

Hey @softmarshmallow

Use the following webpack config which this is being fixed:

module.exports = {
    webpack: (config, {isServer}) => {
        if (isServer) {
            config.externals.push('_http_common');        }
        return config;
    },
    target: 'serverless',
};

Above config is for next js but you can also transfer this to your custom config.

@JamesForan I have been using serverless-bundle which has initial functionality called forceExclude but I know that its underneath is using webpack so there’s an option that this parameter is somehow passed to webpack. You can have a look on it, and it may give you some idea.