nexus icon indicating copy to clipboard operation
nexus copied to clipboard

Is this package still maintained?

Open zakariamofaddel opened this issue 2 years ago • 7 comments

The ecosystem around this project keeps evolving quite rapidly, but it seems that nexus cannot keep up. I completely understand the state of open source, I'm just wondering if I should look for something actively maintained or if there are plans to keep this project going.

Thank you guys!

zakariamofaddel avatar Oct 18 '22 11:10 zakariamofaddel

@see https://github.com/graphql-nexus/nexus/discussions/894

haysclark avatar Oct 28 '22 21:10 haysclark

The ecosystem around this project keeps evolving quite rapidly, but it seems that nexus cannot keep up.

Our team uses Nexus on a daily basis and it works fine. I'm guessing the next major release that I'll cut will be around the GraphQL 17 release. If you're using Prisma, I don't know how well it works because I've never used the Prisma plugin (we use Knex), same goes for federation.

I have started playing with https://pothos-graphql.dev/ and have been very very impressed with the approach it takes to schema construction, type safety, modularity, and plugins. The project is actually inspired by Nexus, aiming to be an abstraction layer without the need for additional code generation. I've been digging into the APIs and figuring out a way that we might be able to layer the two together, to provide an incremental path to move to Pothos' API.

If you're already using Nexus for a project, or you're pretty familiar with Nexus and happy with what it does, feel free to keep using it until there's a more official recommendation on what a Nexus+Pothos integration might look like. Eventually I'd like to provide a fully baked migration approach to bridge Nexus & Pothos incrementally, because I feel like we're after the same things, and they've really nailed the plugin experience, it almost feels like a waste to have two isolated projects. Also, based on how Nexus works internally, it shouldn't be too difficult to bridge the two I don't think.

I'm going to have much more time in 2023 to get things up to date and be more responsive here, will update with additional findings.

tgriesser avatar Dec 17 '22 03:12 tgriesser

cc @hayes

tgriesser avatar Dec 17 '22 03:12 tgriesser

No need to migrate gradually. I built a codemod for doing most of the heavy lifting for you: https://github.com/villesau/nexus-to-pothos-codemod

I used it to migrate our own codebase successfully. There might be different conventions across the codebases so the experience might vary - but I'm more than open for pull requests fixing the issues you might encounter!

villesau avatar Jan 03 '23 11:01 villesau

I hope that this package is still being maintained because we heavily rely on it.

ccfiel avatar Aug 27 '23 22:08 ccfiel

@tgriesser is there any update of this is 2024 - is the recommendation to migrate to Pothos ? - we are still using Nexus but am concerned the last release 1.3.0 was over a year ago - I look forward to you comments

MarkAPhillips avatar Jan 11 '24 11:01 MarkAPhillips