docs VS nestjs-auth-graphql-mikroorm-starter

The syntax plugins for Prisma ORM auto-format their schema files in a similar way [1]. It bothers me so much that I can't bring myself to use their solution - which I realise is incredibly petty :)

[1] https://github.com/prisma/docs/blob/main/content/200-concept...

https://github.com/prisma/docs/issues/1652 It's almost as if when you're biased, you only find what you are looking for.

Ha, thanks a lot for catching this, just fixed it ✅

That's fair! I'm actually with you that proper documentation contributes a lot to a positive developer experience and while it seems like a detail, I totally understand how this feels off putting! I've created an issue for this forwarded it to our docs team to get this fixed very soon. Thanks again for reporting!

What exactly do you mean with a bulk API? As of now, Prisma provides updateMany and deleteMany operations. There's also the $transaction method which you can use for bulk creates and other bulk operations (plus we're also working on extending the Prisma Client API, e.g. with `createMany operations).

GitHub - Jenyus-Org/nestjs-auth-graphql-mikroorm-starter: A NestJS boilerplate with authentication, GraphQL and MikroORM.

Well, the best I can offer is the NestJS starter that I go over in the third blog post I linked. I have two implementations of it, one using TypeORM and one using MikroORM. Other, more complex, projects unfortunately aren't open-source for the time-being, but they all implement the same patterns that I went over in the posts.

The good thing about NestJS at least is that MikroORM has a great integration for it. It may not be first-party but at least it's almost a drop-in replacement for TypeORM and I'm really hoping it starts doing well. I've also started to transition to it for my company and have been working in a boilerplate for this setup if you're curious in checking it out.

I see, thanks! I'm actually working on implementing that in my MikroORM NestJS boilerplate which is a copy of my TypeORM version of that. I'm mostly just a little worried about production performance and stability, but at least MikroORM uses KnexJS under the hood so I have a very familiar query builder to work with if issues arise whereas TypeORM's query builder isn't that great IMHO.