Adds CLI flags to dev build and start to change what is built and run

[borisno2]

Currently, Keystone provides the useMigrations config option to either enable or disable the generation of Prisma Migrations. When useMigrations is false, the default, running keystone dev performs a schema push to the DB and forces a reset if there is any drift. When useMigrations is true running keystone dev will generate the prisma migrations and also reset the DB if there is any drift.

The aim of this PR to give the developer more options when it comes to migrations. The current behaviour remains however the following is added:

• Updates keystone prisma CLI to use the built configuration when the --frozen flag is used so that uncompiled ts files are not required after a build step - helpful when building Docker images without needing keystone.ts and all its dependencies.
• Adds a --no-db-push flag for keystone dev that skips the schema push to the DB when useMigrations is set to false or undefined, used if you don't want to force keystone to use the database you have, for example, an existing DB you don't want to have migrations for.
• Changes the behaviour of build so that it generates the schema files and adds a --frozen flag to build to force it to just validate instead (current behaviour)
• Adds --no-server to dev to run dev without express, useful when not using express - ie Keystone in Next
• Adds --no-ui (dev, build and start) and --no-prisma (dev and build) to build and/or run keystone either without the AdminUI or without Prisma
• Marks useMigrations as deprecated - this config option will be removed in the next major release - use keystone prisma migrate dev to generate database migrations. To mirror existing behaviour of useMigrations use keystone prisma migrate dev && keystone dev --no-db-push

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 13, 2023 at 6:59AM (UTC)

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 3c55c60:

Sandbox	Source
@keystone-6/sandbox	Configuration

[gautamsi]

@borisno2 Am I able to build the admin ui separately yet?

[dcousens]

Moved the removal of --reset-db to #8302, so we can merge this pull request and move forward.

[gautamsi]

What is the reasoning behind deprecation of useMigration? I see it will be removed but I do not understand why.
@borisno2