Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Current state of the project + compatibility with Vulcan #2307

Open
eric-burel opened this issue May 13, 2022 · 0 comments
Open

Current state of the project + compatibility with Vulcan #2307

eric-burel opened this issue May 13, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@eric-burel
Copy link

Hi folks, I am the maintainer of the Vulcan open source project.

We've been developing something very similar to Graphback. Our engine used to be locked in with Meteor, but we have spent the last 2 years migrating to NPM packages and Next.
We eventually made our engine available as "Vulcan Fire". We maintain a very complete Next.js starter, an Express starter for long running tasks, and work on a Remix starter as well.

The difference mainly lies in the fact that we propose JavaScript model, while Graphback seems to prefer designing them in GraphQL.

I'd like to know whether you plan to maintain Graphback in the long run and more broadly what's the current state of the project.

I've opened a ticket at Vulcan to explore the compatibility with Graphback (VulcanJS/vulcan-npm#122), I think it would be pretty easy to convert Vulcan model to Graphback model and vice-versa, making both technologies compatible if that can be interesting for our users.

@eric-burel eric-burel added the enhancement New feature or request label May 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant