Incorrect bundling of dependencies

[RobertAron]

Link to the code that reproduces this issue

https://github.com/RobertAron/deploy-issue-recreate/tree/weird-home-page-behavior

To Reproduce

1. Deploy to vercel (default turbopack deploy. You'll need a db setup)
2. open the page /other
3. The action will crash with the following logs:

PrismaClientInitializationError: 
Invalid `prisma.legend_levels.findMany()` invocation:


Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".

We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.

This is likely caused by a bundler that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" next to the resulting bundle.
Ensure that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied next to the bundle or in "../../../node_modules/@prisma/db-schema".

We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-bundler-investigation

The following locations have been searched:
  /var/node_modules/@prisma/db-schema
  /var/task/apps/console/.next/server
  /vercel/node_modules/@prisma/db-schema
  /var/task/apps/console/.prisma/client
  /tmp/prisma-engines
    at Bn.handleRequestError (/var/task/apps/console/.next/server/chunks/6829.js:121:7559)
    at Bn.handleAndLogRequestError (/var/task/apps/console/.next/server/chunks/6829.js:121:6598)
    at Bn.request (/var/task/apps/console/.next/server/chunks/6829.js:121:6305)
    at async a (/var/task/apps/console/.next/server/chunks/6829.js:130:9498)
    at async Promise.all (index 0)
    at async /var/task/apps/console/.next/server/app/game-legend/page.js:5:218
    at async c (/var/task/apps/console/.next/server/app/game-legend/page.js:5:1103) {
  clientVersion: '6.3.1',
  errorCode: undefined,
  digest: '3211781341'
}

Current vs. Expected behavior

Actions are bundled with all of their dependencies.

Provide environment information

Only on vercel deployments.

Which area(s) are affected? (Select all that apply)

Webpack, Server Actions, Module Resolution

Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

Additional context

I've tried so many things here and I'm convinced this must be a bug.

Weird behaviors:

• Adding an action that uses prisma to the / page fixes it on the /other page.
• Removing the inner async layout fixes the action

I'm pretty convinced this is not a bug with prisma. I spent a lot of time trying to find bugs with their "nextjs-mono-repo-workaround" plugin and I'm fairly sure it's correctly copying over the binaries and adding them to the node trace files. Additionally changes to seemingly unrelated components can break the action, so it seems likely to me this is a bug with vercel.

[RobertAron]

Canary also does not resolve the issue:
https://github.com/RobertAron/deploy-issue-recreate/tree/try-canary

[RobertAron]

I did look at this discussion. This comment in particular looks really promising but unfortunately it doesn't apply to this situation, as I don't have the prisma package being optimized.

Also just to reiterate the part that I think is really relevant...

• Adding an action that uses prisma to the / page fixes it on the /other page.
• Removing the inner async layout on /other fixes the action

So editing code that doesn't really interact with the action at all seems to somehow effect how things are being bundled.

Unfortunately there are a lot of different situations that can cause this error to happen since bundling executable is not very common.

[bwegrzyn]

Were you able to find a solution to this? I am also facing this issue, and it seems I cannot get libquery engine bundled in the build.

[RobertAron]

There's a lot of reasons why the libquery engine wont get bundled, but if you're stuck in the same place I am, then the only option is to use routes instead of actions 🙃

[o3osatoshi]

I’m facing the same issue too 😔

[o3osatoshi]

I resolved the issue as follows:

1. Use a monorepo structure
2. Place Prisma in a shared package
3. Import Prisma from the package in both actions and routes
4. Use the Prisma plugin: @prisma/nextjs-monorepo-workaround-plugin

For details, please refer to my sample repository.
https://github.com/o3osatoshi/experiment/tree/e3d2ca48492dc2851a7055f96df607357d15d8d4