[Suggestion] Move all Prisma packages to the `@prisma` scope

Hi,

just thought I’d voice a suggestion to move all of Prisma’s packages to the @prisma scope. Currently there is both nexus and @prisma/nexus with the docs for nexus-prisma referencing @prisma/nexus but depending on nexus itself.

When Babel made the change to scoped packages about a year or two ago, that made finding any and all official packages so much easier. I think the same could be said for Prisma. Having an umbrella to search under will make finding/discovering packages made by the organization so much easier. It will also allow the organization to release community “owned” (i.e. not a repo by the prisma user) under the umbrella if they deem it fit and then the package will have a ‘Seal of Approval’.

Just a thought, but I think it would be a nice change.

[timsuchanek]

That’s a great point, I also like that. We’ll discuss it internally!

[schickling]

All Nexus-related packages will most likely be published under the @nexus NPM namespace in the future.

We’re also planning to publish all JS-based Prisma tools under the @prisma NPM namespace.