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

Graphql 16.2.0 support #797

Open
st33fn opened this issue Dec 23, 2021 · 9 comments
Open

Graphql 16.2.0 support #797

st33fn opened this issue Dec 23, 2021 · 9 comments

Comments

@st33fn
Copy link

st33fn commented Dec 23, 2021

Currently I'm facing the 'Could not resolve dependency' err upon installing the express-graphql. Any info on this?

Thanks guys!

@jnv
Copy link

jnv commented Jan 11, 2022

Hey, this is duplicate of #790. There is a PR #793 to fix that (among other things).

@ste2425
Copy link

ste2425 commented Jan 12, 2022

I think its fair to say this project is no longer maintained, even with regular community PR's being made. Might be best to find an alternative, we are.

@adviner
Copy link

adviner commented Jan 12, 2022

Is there an alternative solution? Working with node and express all Googling solutions always point to express-graphql. Trying to find a solution that doesn't require express-graphql or other dependencies. How do others use it? If everyone is depending on this library, we are all in trouble.

@jnv
Copy link

jnv commented Jan 13, 2022

My colleague reached out to maintainers on the community Discord and the good news is that there should be a new release soon-ish, so 🤞.

I have also researched alternatives and I'd say the most promising one is graphql-helix, it's somewhat more minimal but also server-agnostic and there is pretty good tutorial to get it running with Express.

@romainPrignon
Copy link

I couldn't wait anymore, so I fork the project: https://github.com/GeorgesTech/express-graphql
Changes: https://github.com/GeorgesTech/express-graphql/pull/1
And I used it like this:

{
  "express-graphql": "https://gitpkg.now.sh/GeorgesTech/express-graphql/npmDist?chore/graphql-16",
}

gitpkg.now.sh allow me to target npmDist folder during install

I do not plan to maintain the fork for a long time
I hope the issue will resolve soon

In the meantime, renovate/dependabot is happy

@dennisMeeQ
Copy link

My colleague reached out to maintainers on the community Discord and the good news is that there should be a new release soon-ish, so 🤞.

I have also researched alternatives and I'd say the most promising one is graphql-helix, it's somewhat more minimal but also server-agnostic and there is pretty good tutorial to get it running with Express.

I made the switch from express-graphql to graphql-helix today. Quite straightforward.

lolopinto added a commit to lolopinto/ent that referenced this issue May 21, 2022
@romainPrignon
Copy link

I moved to https://www.graphql-yoga.com/ V2 from https://www.the-guild.dev/

there is a migration path from express-graphql: https://www.graphql-yoga.com/docs/migration/migration-from-express-graphql
The migration was easy for me.
I just had to replace some middlewares with https://www.envelop.dev/ plugins also from the-guild

If you happened to use the fork: https://github.com/GeorgesTech/express-graphql
I'll keep the fork public for 1 month
I'll delete it at the beginning of Jully

Happy migration :)

@BlueSialia
Copy link

For those interested, I also forked the project at https://github.com/BlueSialia/express-graphql.

The company I work at uses it for a project, so I will be maintaining it for a long while.

Be aware that I made some changes already to the library, so just replacing express-graphql with @bluesialia/express-graphql may not be enough in some cases.

@enisdenjo
Copy link
Member

This library has been deprecated and this repo will be archived soon. It has been superseded by graphql-http.

Furthermore, if you seek a fully-featured, well-maintained and performant server - I heavily recommend GraphQL Yoga!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants