Proposal: Move `prisma2` CLI into `@prisma/cli` npm package

We’re considering moving the prisma2 CLI from the prisma2 npm package into @prisma/cli similar to how ionic, Angular and vue are doing it.

Note that you’ll still invoke the CLI via the prisma2 command. For a global installation, this would be the upgrade flow:

$ npm uninstall -g prisma2
$ npm install -g @prisma/cli

# Invoke the new CLI from the new package:
$ prisma2 --help

Note that we’re planning to change the prisma2 command to prisma upon the upcoming Prisma 2.0 launch.

Pros

• Clearer package naming (“you know what you get”) • Easier to distinguish versions of individual packages • More consistent: Unifying Prisma’s tools under the @prisma npm scope

Cons

• Another breaking change • Easier to find/remember/understand when CLI package name and command are identical (e.g. netlify-cli npm package and netlify CLI command is one additional thing to remember)

[janpio]

As we also own prisma, we could in theory make npx prisma (the last case, that does not work for npx vue) work and tell the use to use the correct command once (and uninstall the prisma package again (or even to it semi automatically in the postinstall). But that would still be confusing, because after adding the local @prisma/cli dependency, the same command that just told them to do someething would then be the valid command to use the CLI.

[homoky]

I know that everything is in development phase right now, but I would really consider to think the most about those things in the beginning. For the newcomers and the community itself is not best to change regularly names of those things. Take example of Photon and Lift, it was strongly communicated and now it is renamed. For my viewpoint it makes harder to wrap your head around prisma2 to keep updated to those late updates.