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
Consider renaming the @prisma/sdk
package to reduce confusion
#10725
Comments
Yeah it should be renamed to be like "common" or "helpers" cause a lot of people think that it's an API for external usage from its name, but it's a really good point that this is a breaking change cause there are a lot of repositories depending on |
Thanks @YassinEldeeb for your feedback! Note: We are considering adding a deprecation message soon and rename it for future major Prisma version (date undefined yet) |
[Internal] Me, Pierre and Alexey created a draft of a plan the renaming |
Can we move this issue to "done"? |
The internal package
Making the intended use of that package explicit (internal only) is important as it helps to manage expectations with users. This is technically not a breaking change as usage of the If you are using this package, it would be helpful if you could help us gain an understanding of where, how and why you are using it. Your feedback will be valuable to us to define a better API. Please share this information at #13877 - Thanks! npm packages |
The name
@prisma/sdk
is a bit confusing since it's not really an SDK, so we might consider renaming it. Based on this internal Slack convo:The text was updated successfully, but these errors were encountered: