dead-deps — what happened to your dependencies

Is express-graphql still maintained?

No — express-graphql stopped being maintained around November 2020. graphql-http is the same idea rebuilt from scratch.

Status
No longer maintained
Last maintained
November 2020
Use instead
graphql-http — on npm
Succession
Reimplementation
Drop-in
no — expect code changes
Confidence
high

What should I use instead of express-graphql?

graphql-http is the same idea rebuilt from scratch. graphql-http is not a drop-in replacement, so expect to change call sites.

How to migrate from express-graphql to graphql-http

Swap graphqlHTTP({schema}) for createHandler({schema}) imported from graphql-http/lib/use/express; GraphiQL is no longer bundled, so run a separate IDE such as ruru (npx ruru -SP -p 4001 -e http://localhost:4000/graphql) if you relied on the built-in one.

Why express-graphql is on this list

express-graphql was the GraphQL reference HTTP handler for Express. Its last release was 0.12.0 in November 2020, and the repository was archived on 20 March 2023 with a README section headed "Say hello to graphql-http", the new reference implementation of the GraphQL over HTTP specification. The npm notice repeats the recommendation and links to a migration document.

The succession is settled: primary sources agree and the ecosystem has already moved.

express-graphql alternatives

Beyond the primary recommendation, these are credible for express-graphql's use case:

Check your own project for express-graphql

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If express-graphql is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.