Are you using Nexus in production? Tell us about it! #830
Replies: 15 comments 5 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Do you use Nexus in production? How long? Due to reasons we are not "in production" yet (i.e. the product isn't open to public). If not now, will you use Nexus in production in the near future? Nexus is my go to library for building GraphQL schema's. Unless Apollo tooling suddenly shifts gears into adopting Code First I don't see myself changing. What is your main reason for using Nexus?
What is the main benefit to date you've experienced from Nexus?
And lastly, this is rather subjective, but Nexus for me sits in the sweet spot of a library and framework. It does one thing well, which is help me build GraphQL schemas, it doesn't force me into anything else (like how to structure my code, if I should use an ORM, if I should use DataLoader, ...) Anything you would love to see from Nexus in the future? I hope first and foremost that Nexus stays in that sweet spot I described above. I love that I can get so much power from such a relative small tool without getting an overload of extra's. Ever since plugins got added (been using Nexus in hobby since it first came out publicly) I've been amazed at what you can do with it. So I would love to see more innovation in that space, not just from Nexus itself but also from community I think there's opportunities to build some super cool stuff. My biggest suggestion for improvement would be that the documentation needs work. Nexus is a super powerful tool but for someone who is relatively new to the GraphQL community the documentation is a wasteland. Some suggestions:
|
Beta Was this translation helpful? Give feedback.
-
|
Do you use Nexus in production? How long? Not yet (almost) If not now, will you use Nexus in production in the near future? Release date is gonna be next week. What is your main reason for using Nexus?
What is the main benefit to date you've experienced from Nexus?
Anything you would love to see from Nexus in the future?
|
Beta Was this translation helpful? Give feedback.
-
Yes, for 3 months.
It has amazing prisma integration and I was looking for a very productive tech stack. I am also using code generator to create react-hooks for apollo-client.
See above, Prisma integration. Super productive stack. Just works.
More examples. I had a hard time getting Unions to work for me. |
Beta Was this translation helpful? Give feedback.
-
Yes, for 20 months.
Code first SDL & Prisma integration.
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Do you use Nexus in production? How long?Yes. Very recently. If not now, will you use Nexus in production in the near future?N/A What is your main reason for using Nexus?Type-safety, type generation. code-first, placing implementation near the definition. What is the main benefit to date you've experienced from Nexus?Easy to write. Easy to use with async/await. Anything you would love to see from Nexus in the future?Awaiting generation. I've been using generation under the full control separately from serving. Namespacing or something like that, to acheive sharing prefix or preprocessing? I'm not so familiar with graphql, and nexus plugin at all, I don't know if it is feasible now or not. |
Beta Was this translation helpful? Give feedback.
-
|
Do you use Nexus in production? How long? If not now, will you use Nexus in production in the near future? What is your main reason for using Nexus? What is the main benefit to date you've experienced from Nexus? Anything you would love to see from Nexus in the future? |
Beta Was this translation helpful? Give feedback.
-
Partial, I used it on development normally but on production I composed from generated GraphQL schemas & resolvers manually because reducing bundle size for serverless (e.g. Cloudflare worker) from 7 MB => 0.5 MB. Working perfectly for six months.
Code First Implementation style
I have been using GraphQL file for years without writing it. |
Beta Was this translation helpful? Give feedback.
-
3 .What is your main reason for using Nexus?
import { extendType } from 'nexus'
export const UserExtended = extendType({
type: 'User',
definition(t) {
t.string('foo')
},
})I got type of t is any. And if include in main project via export * from 'extended-schema'i have extended GraphQL schema, but does not got errors in resolvers due no data for required field foo. Anyway, Thanks for awesome project! |
Beta Was this translation helpful? Give feedback.
-
We've used Nexus for our billing microservices at A Cloud Guru for 2 years - almost exactly, since
Programmatic schema generation allowed us to reduce duplication in type definitions.
Improving type safety between the schema and our service logic, especially binding generated enums to our union types so input types and resolver params are kept in-sync.
Nexus itself is great and we'd just like to see stability and maintenance continue. We are looking at approaches with tools like GraphQL Code Gen, to bring better type safety to development on frontends. We'd love to see docs for best practice and patterns on using Nexus in different stacks. Our backend is fully serverless and it took some time to understand the "Abstracted Reflection System" and I'm still not sure we've found the best approach. Would love to see more examples for that scenario. I also use Nexus with personal projects and am following the integration with with Prisma closely. 😍 Love your work team. Many thanks from Melbourne! ✋ |
Beta Was this translation helpful? Give feedback.
-
Yes! We're really enjoying Nexus at Fieldguide and have been using it for the past six months. It powers our Apollo Server application, integrated with Hasura as a remote schema. We just wrote about our technology stack, which explains this setup in more detail.
Prior to integrating Nexus, we were following more of a schema-first approach, writing separate GraphQL types and TypeScript resolver configurations, which could easily get out of sync (not to mention, it was annoying to duplicate things across both languages). We were looking for a TypeScript-first alternative right around the time Nexus hit v1.0.
The inherent type-safety and code generation has accelerated and de-risked our server-side development. In particular, the "reflection" concept provides a really great developer experience.
Thank you for the wonderful project, and keep up the great work! |
Beta Was this translation helpful? Give feedback.
-
Brought it into my current role at https://haldi.com and we've been using it in production for over a year now. Prior to that I used it at thredup.com as well.
Yes, I'll be using it again
You said it best
Generally speaking with GraphQL it's all about types... We use GraphQL CodeGens to generate types across all our apps and that alone is hugely beneficial.
The ability to reuse the
Love what your guys are doing over there, keep up the great work 💯 👩💻 👏 🧑💻 |
Beta Was this translation helpful? Give feedback.
-
|
I wonder if you guys are still using it. |
Beta Was this translation helpful? Give feedback.
-
|
Left it months ago |
Beta Was this translation helpful? Give feedback.
-
What are you using instead now? |
Beta Was this translation helpful? Give feedback.
-
|
https://pothos-graphql.dev/ is a great replacement |
Beta Was this translation helpful? Give feedback.
-
|
Personally I am at a new organization and we're dipping our toes into NestJS. |
Beta Was this translation helpful? Give feedback.
-
As we near toward 1.0 we're interested to hear from folks who use Nexus in production. We might even be interested in incorporating your story (with your permission, of course) into the 1.0 blog post that Prisma will publish.
Here are some questions:
Beta Was this translation helpful? Give feedback.
All reactions