[Next.js + Now serverless] Can't resolve 'child_process' in './node_modules/@prisma/photon/runtime'

I am using preview019 with a SQLite db

Photon sits in a file and being used everywhere

import { Photon } from "@prisma/photon";

export const photon = new Photon();

The initialization caused the problem if I change that to something like export const photon = 123;, then this error goes away.

Maybe I get the initialization wrong? Should not reuse this instance?

The project is next.js v9, api is Now serverless, sits in pages/api

After running next, the 1st render to index works, but go to any page will show the following error:

However, api is working: /api/graphql is working:

anything to do with https://github.com/prisma/prisma2/issues/1021 ?

[guillaumeLamanda]

I here 👋

I made a minimal reproduction of the child_process error with Next.js.
https://github.com/guillaumeLamanda/nextjs-prisma

Hope it can help

[kmturley]

I had a similar issue. It seems that a generic package import, traverses all files underneath regardless of whether the methods are actually called:

import { clientSideMethod } from 'mypackage'

Actually first goes to the root index.js inside the package and calls:

export * from './file'; // contains server-side code
export * from './utils'; // contains client-side code only

Therefore the error was triggered. Solutions are:

1. Use a more specific import import { clientSideMethod } from ‘…/…/node_modules/mypackage/dist/utils’
2. Dynamically import server-side modules when needed
3. Split packages or modules into client-side vs server-side

Very simple to fix, but frustrating to find the cause!