finds.dev← search

// the find

graphql/graphiql

★ 16,859 · TypeScript · MIT · updated Jul 2026

GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.

The official GraphQL IDE and LSP ecosystem, covering everything from the browser-based GraphiQL playground to editor integrations for VS Code, CodeMirror, and Monaco. It's the canonical tooling layer for GraphQL development — if you're building anything that needs GraphQL editing support, this is where you start.

The language service is shared across all editor targets (CM5, CM6, Monaco, LSP server), so schema-driven autocomplete and validation are consistent everywhere rather than each integration reimplementing its own parser. The monorepo structure with changesets makes versioning tractable across 15+ packages that have real interdependencies. The VSCode extension ships as three separate packages — syntax, language features, execution — so consumers can take only what they need without pulling in the whole stack. Active maintenance is genuine: the repo pushed yesterday and has a real working group with scheduled meetings.

The XSS warning at the top of the README is for versions from 2021, yet it's still the first thing you read — it's historical noise that erodes confidence in current users who don't read carefully. The monaco-graphql package is described as 'in the works' in the README despite existing and being published, which suggests the docs lag the code. The plugin API is described as 'fielding proposals' with no timeline, which means anyone building on the plugin surface is betting on an interface that hasn't stabilized. Bundle size for the full graphiql package is non-trivial and there's no lazy-loading story for the doc explorer or history panel when you embed it in a production app.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →