-
Notifications
You must be signed in to change notification settings - Fork 86
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
Upcoming rename of @prisma/sdk
to @prisma/internals
with Prisma 4
#130
Comments
Note: You can try prisma packages on the |
@CarterGrimmeisen Prisma 4.0.0 was published on Tuesday 🛶 The internal package
If you’re using If you know people affected by this, feel free to point them to the GitHub discussion. |
Hey,
Jan from Prisma Engineering here.
Quick heads up that we will soon rename our
@prisma/sdk
package to@prisma/internals
with Prisma 4, which we plan to release on June 28th (soon!).The
@prisma/sdk
package was meant as an Prisma internal package only, but somehow it leaked out over time and is now used across all kinds of tools - including yours of course 😄With the rename of the Npm package we want to make it clearer that we can not give any API guarantees for
@prisma/internals
, might need to introduce breaking changes to the API from time to time and will not follow semantic versioning (breaking changes only in major upgrade) with it. We think that it is better communicated withinternals
than withsdk
.With Prisma 4, besides the package name nothing should change though.
Additionally it would be super helpful if you could help us gain an understanding where, how and why you are using
@prisma/sdk
(soon@prisma/internals
, remember 😀) to achieve, what exactly. We want to cleanup that package and your feedback will be valuable to us to define a better API.Looking forward to your feedback.
Best
Jan & your friends at Prisma
PS: Are you using
Prisma.dmmf
fromimport { Prisma } from '@prisma/client'
in your code somewhere by chance? That will also change soon and not include thePrisma.dmmf.schema
sub property. Instead you can usegetDmmf
from@prisma/internals
moving forward.The text was updated successfully, but these errors were encountered: