Consider renaming the `@prisma/sdk` package to reduce confusion
See original GitHub issueThe 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:
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Prisma 4.0.0 Release - GitClear
Renaming of @prisma/sdk npm package to @prisma/internals. The internal package @prisma/sdk is now available under the new, more explicit name @ ...
Read more >What's new in Prisma? (Q2/2022)
We've removed the internal Prisma.dmmf.schema to reduce the size of Prisma Client generated and improve boot times in Prisma 4. To access the ......
Read more >Let's Learn Prisma! - Learn With Jason
With Prisma 1, this API that was generated in GraphQL was why intended to serve the actual GraphQL API layer and make it...
Read more >Available CRAN Packages By Date of Publication
Available CRAN Packages By Date of Publication. Date, Package, Title. 2022-12-25, BDgraph, Bayesian Structure Learning in Graphical Models using Birth-Death ...
Read more >Command Line Interface | RedwoodJS Docs
api /dist and Webpack to package the web side into . ... Running yarn redwood build without any arguments generates the Prisma client...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
[Internal]
Me, Pierre and Alexey created a draft of a plan the renaming https://www.notion.so/prismaio/Renaming-prisma-sdk-and-cleaning-up-internal-packages-f217f9ba96aa40fd91f47995b9266dc3 Work in progress, nothing planned yet, but this would be the general direction we want to go for.
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)