Prisma: 2.0.0-preview-9 Release

Today, we are issuing the ninth Preview release: 2.0.0-preview-9 (short: preview-9).

Major changes

For this release, we have invested a lot into making the prisma2 init command a lot more approachable and user-friendly. The wizard that's launched by prisma2 init helps you to set up a new project. With this release, the wizard becomes a lot more robust and provides a clearer user flows than before.

Try it yourself by upgrading to the latest version and using the init command:

npm install -g prisma2
prisma2 init hello-world

Please share your feedback for the init flow and report any issues you might encounter.

Fixes and improvements per Prisma 2 repository

prisma2

• Prisma starter in init already has migrations
• use rewritten introspection in migration engine
• [EPIC] Move prisma 2 rust code from prisma repo to somewhere else
• Zeit Now Deployment
• Serverless (Faas) compatibility
• [Suggestion] Optimize the Prisma2 Spec Document Example
• Documentation should clarify not implemented features
• Cannot use @relation(id) to specify the side of the relation
• Prisma2 and Docker
• Prisma2 CLI is binary on Ubuntu 16.04 doesn't link to install libssl
• ID not incremented on MySQL and Postgres
• Fetch the correct binary for EC2 started with Amazon Linux 2 + x86
• Create a Windows Binary

Fixed by the new init flow

• ENOENT running prisma2 init
• Init flow requires an empty directory
• Prisma CLI merges graphql and graphql-auth examples when "GraphQL Boilerplate" is selected in `prisma2 init
• EPIC Implement new prisma init CLI flow
• When connecting to existing MySQL, prisma2 init wizard ends at the introspect step and does not select prisma tools ( Photon, Lift ) nor generate any boilerplate.
• CLI generated undefined when you enter and delete a field in database credentials flow.

photonjs

• Add pretty datamodel parser error for get_config