Hi, we have many prisma1-nexus-graphql-typescript ...
# mongodb
m
Hi, we have many prisma1-nexus-graphql-typescript microservices with mongodb and are trying to upgrade them to prisma2, but the prisma init fails with
We detected a Prisma 1 project.... If you want to upgrade to Prisma 2+, please have a look at our upgrade guide
. I used this upgrade instruction site (https://www.prisma.io/docs/guides/upgrade-guides/upgrade-from-prisma-1/upgrade-from-mongodb-beta), but it fails on prisma init. Currently there is no prisma or prisma1 folder present. What can I do ? -> this seems to be due to
prisma.yml
, if you rename that everything works fine. This should be added to the docmumentation, because it seems to happen to many people.
1
n
Hey Martin 👋 Here’s another slack thread in which we were discussing the same issue https://prisma.slack.com/archives/CA491RJH0/p1652089083656559
Oh I just saw, Renaming
prisma.yml
solved the issue for them
m
yes, thank you, that solved this first problem. ;)
Now I have to find an up-to-date instruction to migrate nexus
n
That guide still needs to be updated, Nexus Prisma is still in early preview: https://github.com/prisma/nexus-prisma/