Hey everyone, we have a few pieces of news we want to share. 🙂 prisma labsFirst up is that we’re quietly launching Prisma Labs. This is a branch of Prisma focused on the ecosystem around Prisma Framework. The Labs team will be led by myself in collaboration with @weakky and overseen by @schickling. The Labs team will be focused this quarter on Nexus, a code-first approach for writing GraphQL APIs. We’ll continue to push forward in close collaboration with @tgriesser on the core (the original Nexus visionary), while also investing heavily on realizing the awesome potential of the nexus-prisma plugin. A number of GitHub repos currently under

prisma/*

have migrated to

prisma-labs/*

. We’ve setup #labs and our sprint work is public at https://github.com/orgs/prisma-labs/projects/1. The Labs team is eager to find transparent ways of working. --- 🚥 Second up is our announcement that starting with

nexus-prisma@0.4

support for Prisma 1 will be dropped. For those following the repo you’ve probably already sensed this coming, but we want to make this official and clear so that you can plan accordingly sooner than later. All current and future Prisma 1 specific GitHub issues have been/will be marked with a

note/prisma1

label. You can expect these issues to generally not be worked on by the core team. In the future we will probably also close these issues as

note/wontfix

to bring further clarity. Finally, expect a migration doc soon. We realize early adopters who invested heavily into

nexus-prisma@0.3

may feel left out here. Please do chime in with any feedback you have in our tracking issue for this change at https://github.com/prisma/nexus-prisma/issues/378. --- 🌱 Thirdly is a state-of-nexus-prisma update. Over the next couple of weeks we will be rolling out various meta-infrastructure improvements to improve project velocity and health. Some of these include: 1. CI/CD releases so that you get value as soon as its ready (https://github.com/prisma/nexus-prisma/issues/379) 2. Rich changelog so that you can catch up on changes quickly and better use tools like renovate that will put this information right into your pull-requests (https://github.com/prisma/nexus-prisma/issues/407) 3. Giving you control over which version of

nexus-prisma

your app depends on (no longer bundled inside Prisma 2 CLI) and using as a regular node library rather than a Prisma 2 generator (https://github.com/prisma/nexus-prisma/issues/395) 4. Revamping the docs and app examples (https://github.com/prisma/nexus-prisma/issues/380) 5. Revamping out issue labelling system (https://github.com/prisma-labs/issues/issues/1) While perhaps not as exciting to you as product improvements, we’re optimistic for how this streamlined automation will facilitate team focus, and we think users will gain too with more transparency into our work and tighter feedback loops. As we iron out our processes, expect these patterns to be rolled out across more of Labs’ projects too. We hope this underscores our commitment to

nexus-prisma

and what may come in the future. Mapping your data layer to your API layer should be safe, easy, fun, and flexible. It’s a key part of making data easy, Prisma’s mission. You should be able to focus on the design decisions and evolution of the mapping, while being mostly freed from its plumbing. You should at all times be able to summon a macro view of your mapping topology and generally be confident that the wiring from A-Z is bug free. And so a primary Q4 objective for the Labs team is reaching a 1.0 iteration on nexus-prisma. But of course the mapping space is a nuanced beast with a huge design surface. 1.0 will be but a start. We’re excited to explore bold new ideas come 2020 sourced as much, we hope, from not just our own internal idea bank but the broader nexus and

nexus-prisma

community. 🙏🏻 🚀