Issue with Waku and Prisma

[skorotkiewicz]

It seems impossible to use databese Prisma with waku, how can I use Prisma with Waku?

Failed to resolve entry for package "@prisma/client". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." specifier in "@prisma/client" package

[dai-shi]

https://unpkg.com/browse/@prisma/[email protected]/package.json

Maybe, "default" in "import" is missing.

https://publint.dev/@prisma/[email protected]

Hmm, it looks okay. It should pick the root default then.

Thanks for reporting. I'm not exactly sure where is the problem, but there must be something.

[dai-shi]

So, there are three issues.

Module resolution issue

As I noted, adding "default" fixes it.

--- node_modules/@prisma/client/package.json.orig	2025-01-23 09:56:21
+++ node_modules/@prisma/client/package.json	2025-01-23 09:56:45
@@ -50,7 +50,8 @@
         "edge-light": "./default.js",
         "workerd": "./default.js",
         "worker": "./default.js",
-        "browser": "./index-browser.js"
+        "browser": "./index-browser.js",
+        "default": "./default.js"
       },
       "default": "./default.js"
     },

Alternatively, you can specify "node" condition explicitly.

// waku.config.ts
import { defineConfig } from 'waku/config';

export default defineConfig({
  unstable_viteConfigs: {
    common: () => ({
      ssr: {
        resolve: {
          conditions: ['node'],
        },
      },
    }),
  },
});

(vite.config.ts can do the same.)

See also: remix-run/react-router#12610

ESM issue (DEV only)

This works:

import { default as Prisma } from "@prisma/client";

const prisma = new Prisma.PrismaClient();

Bundling issue

See vitejs/vite#19036 and its workaround.

---

In summary, this seems too tricky, and there's nothing particular that Waku can do. But, if anyone has suggestion for possible fixes, feel free.

[tylersayshi]

Should this be flagged to https://github.com/prisma/prisma ? They may be open to just changing the exports field.

[dai-shi]

Feel free to do it, but there might be already something filed.

[tylersayshi]

oh wow they have a lot of open issues... I'll leave that up to @skorotkiewicz about whether or not to file a new issue over there.