fix(client): replace dynamic import for wasm-worker-loader with static export

[smorimoto]

Fixes #23600

As I understand, since dynamic import is not necessary here, we can easily fix the linked issue.
Is there anything I am missing?
I'm actually using this patch in my runtime environment and I don't see any performance issues either.

[CLAassistant]

All committers have signed the CLA.

[jkomyno]

Thank you @smorimoto for this PR.
I think the next course of action for us is to merge this and observe the impact on our ecosystem-tests.

To summarise the context around this PR for other internal reviewers:

• Next.js uses a non-standard top-level await plugin, which can conflict with how we use import the Wasm Query Engine in Prisma: Top level await with SWC vercel/next.js#31054
• Some users reported similar errors on Next.js + other libraries different than Prisma: Edge runtime causing terser panic due to top level await vercel/next.js#64792 (comment)
• Some of the Next.js + Prisma users reported that the patch provided by this PR works: Next.js app build fails when using Prisma with DB driver in Server Action #23600 (comment)
• It looks like recent versions of Next.js 14 recently surfaced this problem to runtime = "edge" users: Edge runtime causing terser panic due to top level await vercel/next.js#64792 (comment)

[Vinlock]

Nice! Glad this is getting fixed. Thank you 🙏🏼 🙏🏼 🙏🏼 🙏🏼

[smorimoto]

@jkomyno We migrated some of our projects to the Node.js runtime for performance, but we're still using this patch for some projects that use the Edge runtime, and we don't see any issues, and in theory we don't expect any issues. What are your concerns about merging this?

[jkomyno]

Hi @smorimoto, here's some updates on our side:

• This patch currently causes esbuild compilation issues when building CommonJS packages, as evidenced by the error in these ecosystem tests:

  Top-level await is currently not supported with the "cjs" output format

• My first alternative version of this PR, feat(client): try CJS-friendly alternative to https://github.com/prisma/prisma/pull/23754 #24029, fixes that problem but unfortunately introduced a new problem when using Next.js with Edge middlewares, or Vercel Edge Functions:

  TypeError: WebAssembly.Instance(): Argument 0 must be a WebAssembly.Module

• Finally, we fixed all of these problems in fix(client): fix dynamic wasm imports for Next.js Middlewares / Vercel Edge in @prisma/client #24312, which we merged yesterday.

As posted in #23600 (comment), may you please another new unofficial version of Prisma, and report back if it keeps working for your scenario? 5.15.0-integration-client-dynamic-wasm-imports.1

You can quickly install it via:

pnpm add -D prisma@5.15.0-integration-client-dynamic-wasm-imports.1;
pnpm update "@prisma/*" 5.15.0-integration-client-dynamic-wasm-imports.1

(please double check that prisma generate has run before retrying).
We expect this to be released with Prisma 5.15.0 next week. Thanks!

[jkomyno]

Hi @smorimoto, here's some updates on our side:

• This patch currently causes esbuild compilation issues when building CommonJS packages, as evidenced by the error in these ecosystem tests:

  Top-level await is currently not supported with the "cjs" output format

• My first alternative version of this PR, feat(client): try CJS-friendly alternative to https://github.com/prisma/prisma/pull/23754 #24029, fixes that problem but unfortunately introduced a new problem when using Next.js with Edge middlewares, or Vercel Edge Functions:

  TypeError: WebAssembly.Instance(): Argument 0 must be a WebAssembly.Module

• Finally, we fixed all of these problems in fix(client): fix dynamic wasm imports for Next.js Middlewares / Vercel Edge in @prisma/client #24312, which we merged yesterday.

As posted in #23600 (comment), may you please another new unofficial version of Prisma, and report back if it keeps working for your scenario? 5.15.0-integration-client-dynamic-wasm-imports.1

You can quickly install it via:

pnpm add -D prisma@5.15.0-integration-client-dynamic-wasm-imports.1;
pnpm update "@prisma/*" 5.15.0-integration-client-dynamic-wasm-imports.1

(please double check that prisma generate has run before retrying). We expect this to be released with Prisma 5.15.0 next week. Thanks!

I'm now closing this PR in favor of #24312, which was merged and is part of the upcoming Prisma release, 5.15.0 (coming out today!).

Thanks @smorimoto for the inspiration and contribution!

[smorimoto]

@jkomyno All right. It would be more polite to set me and @nzws as co-authors on Git from now on :)
https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors