Upcoming rename of `@prisma/sdk` to `@prisma/internals` with Prisma 4 about prisma-appsync HOT 5 CLOSED

Hey @janpio, thanks for letting me know!

Removing @prisma/sdk entirely from Prisma-AppSync will not be an issue, as I’m only using it for its parseEnvValue function (which I was planning to remove in the next coming release). I am also not using Prisma.dmmf from @prisma/client anywhere.

Prisma-AppSync is mainly reliant on generatorHandler and DMMF exported from @prisma/generator-helper package, as well as the GeneratorOptions available from the generatorHandler :: onGenerate handler. I am reading the dmmf.datamodel property from there.

Any changes planned on the above?

from prisma-appsync.

Not right now, but good to know - I guess we better start a list of which ones of these APIs are used externally, so we can better anticipate if any changes will cause trouble.

from prisma-appsync.

Note: You can try prisma packages on the dev tag on npm, like @prisma/[email protected]

from prisma-appsync.

@Jolg42 Thanks! Will look into it.

from prisma-appsync.

@maoosi Prisma 4.0.0 was published on Tuesday 🛶

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 know people affected by this, feel free to point them to this GitHub discussion.
It will help us understand where, how, and why people are using it, so we can define a better API.

Note: I posted your earlier comment of your current usage in that discussion to centralize the usage feedback.

from prisma-appsync.