-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@prisma/extension-pulse is not exported from package #24130
Comments
Hi @jeffreybos 👋🏻 Thanks for raising this. With your NextJS app, are you attempting to use Prisma Pulse in an edge function or serverless function? |
I'm using it with supabase. I followed the prisms pulse guide for setting up my project. But the issue right now is that the installed pulse npm package is not recognized as a module |
I have just encountered the same issue currently. I am also using supabase. |
I have the same issue |
I am using postgresql on railway |
Hey folks! Can you please confirm that you have set |
Hi, i have the same issue, @jeffreybos did you find a solution ? |
@ThomasBnf To confirm, you have set customConditions in your "tsconfig.json" file as mentioned here and are still getting the issue, right? |
yes, exactly, i tried with "customConditions":["workerd"] or ["node"] |
Thanks for confirming. Our team has take a note of this and will get back with further updates. |
Bug description
I want to use Prisma Pulse, but when i import (and ofcourse i installed the package with NPM) the package. I get the following error.
./lib/db.ts:2:0 Module not found: Package path . is not exported from package /node_modules/@prisma/extension-pulse (see exports field in /node_modules/@prisma/extension-pulse/package.json)
I've checked the node_modules and @prisma/extension-pulse is in there
I'm. using NextJS 14.1.4 and Prisma 5.13.0 and @prisma/extension-pulse 1.0.2
How to reproduce
Expected behavior
No response
Prisma information
Environment & setup
NextJS 14.1.4
Prisma Version
Prisma 5.13.0
Pulse 1.0.2
The text was updated successfully, but these errors were encountered: