Hello, Do you recommend to use prisma without Nexus or Nexus prisma plugin? there are some prisma examples where nexus is not used?

Hey @Al 👋 You can use Prisma without Nexus and the plugin. We also have an example here that defines the GraphQL schema separately. Personally I would recommend using Nexus as you can easily define the schema in code and it will create the GraphQL file automatically. Also the added benefit of typings helps a lot when creating resolvers and the schema.

Thanks @Ryan for the comment and link. My doubt is that I tried nexus-prisma-plugin this morning, but from what I see it seems not really stable. So I'm looking for other ways: without Nexus or without Nexus-prisma-plugin. But from your words maybe I could re-evaluate Nexus😉

Could you explain on what parts of Nexus did you find unstable or not easy to work with?

For example The stable version 0.25 has some problems with windows Trying the 0.26.next version, when I run nexus build I receive some errors like "duplicate identifier Prisma" or "cannot find module ....prismaclientindex" I see a similar opened issue on GitHub about that. Then it is not clear how to implement an external identity provider like Auth0 using the jwt-auth-plugin.

Are there issues for these problems? Then I am sure they will be fixed soon.

@Al If you’re facing issues with the Nexus framework, you can always use the standalone component Nexus Schema to get all the feature of Nexus.

Thanks @janpio Yes, I need the graphql API. I'm going to open the issue with build command for your evaluation. Thanks @Ryan probably at the moment nexus/schema is the best way.

I personally find Nexus to be a lot harder to read. I came from Python’s Graphene library which also takes the code-first schema definition, but I prefer SDL file