Upcoming rename of `@prisma/sdk` to `@prisma/internals` with Prisma 4

[janpio]

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 with internals than with sdk. 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 from import { Prisma } from '@prisma/client' in your code somewhere by chance? That will also change soon and not include the Prisma.dmmf.schema sub property. Instead you can use getDmmf from @prisma/internals moving forward.

[Jolg42]

Note: You can try prisma packages on the dev tag on npm, like @prisma/internals@3.16.0-dev.84

[yujonglee]

@janpio @Jolg42 Thanks.

[Jolg42]

@yujong-lee Prisma 4.0.0 was published on Tuesday :canoe:

The internal package @prisma/sdk

• was published for the last time to ease the upgrade (in the future we might reuse the package name, but its content will be different)
• marked deprecated on npm
• available under the new, more explicit package name @prisma/internals.

If you’re using @prisma/sdk (now @prisma/internals), it would be helpful if you could help us understand where, how, and why you are using it by giving us feedback in this GitHub discussion. Your feedback will be valuable to us in defining a better API.

If you know people affected by this, feel free to point them to the GitHub discussion.