-
Notifications
You must be signed in to change notification settings - Fork 1.5k
GraphiQL 4.1 Announcement blog post #2007
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,100 @@ | ||
--- | ||
title: GraphiQL 4.1 is Released | ||
tags: [announcements, grants] | ||
date: 2025-06-01 | ||
byline: Dimitri Postolov | ||
--- | ||
|
||
import { Callout } from "nextra/components" | ||
|
||
I'm thrilled to announce the release of **GraphiQL 4.1**! 🎉 | ||
|
||
Thanks to funding from the **GraphQL Foundation**, I'm working on migrating | ||
GraphiQL to the Monaco code editor — a long-awaited update that's been on our | ||
roadmap for years. | ||
|
||
> In fact, the [original issue](https://github.com/graphql/graphiql/issues/2326) | ||
> was opened over **three years ago**! | ||
|
||
## Roadmap | ||
|
||
Migrating to the Monaco editor is a major milestone, and to ensure a smooth | ||
transition for everyone, I've broken it down into several incremental releases: | ||
|
||
### GraphiQL 3.9 | ||
|
||
- Switched build system from Webpack to Vite | ||
- Compiled the codebase using the new | ||
[React Compiler](https://react.dev/learn/react-compiler) | ||
|
||
### GraphiQL 4 | ||
|
||
- Dropped support for React 16/17 | ||
- Added support for React 19 | ||
- Introduced a refreshed tabs UI | ||
- New ESM-based CDN example | ||
- Deprecated the legacy UMD CDN build | ||
|
||
### GraphiQL 4.1 _(This release)_ | ||
|
||
- Standalone Doc Explorer plugin | ||
- Standalone History plugin | ||
- Migrated state management from React context to | ||
[zustand](https://zustand-demo.pmnd.rs) | ||
|
||
### GraphiQL 5 _(Coming Soon)_ | ||
|
||
- Migration from Codemirror to | ||
[Monaco Editor](https://github.com/microsoft/monaco-editor) | ||
- Replacing `codemirror-graphql` with | ||
[`monaco-graphql`](https://github.com/graphql/graphiql/tree/main/packages/monaco-graphql) | ||
- Support for comments in **Variables** and **Headers** editors | ||
- New examples: **GraphiQL x Vite** and **GraphiQL x Next.js** | ||
|
||
<Callout type="info"> | ||
For the full roadmap, check out the [tracking issue on | ||
GitHub](https://github.com/graphql/graphiql/issues/3874). | ||
</Callout> | ||
|
||
## What's New | ||
|
||
GraphiQL 4 serves as a gateway to the upcoming GraphiQL 5, which will be powered | ||
by the Monaco editor, the same editor used in VSCode. Upgrading to GraphiQL 4 is | ||
an essential step if you're already using React 19. | ||
|
||
We've extracted **Doc Explorer** and **History** into standalone plugins, | ||
allowing full customization of GraphiQL's built-in plugins in the **GraphiQL | ||
5**. | ||
|
||
Under the hood, we've replaced React context with zustand, making the internal | ||
state management simpler and more maintainable, and enabling faster iteration on | ||
new features. | ||
|
||
### Time to Say Goodbye to UMD Builds! | ||
|
||
With React 19, | ||
[UMD builds have been removed](https://react.dev/blog/2024/04/25/react-19-upgrade-guide#umd-builds-removed). | ||
The React team now recommends using ESM-based CDNs like | ||
[esm.sh](https://esm.sh). | ||
|
||
We've updated the | ||
[CDN example](https://github.com/graphql/graphiql/tree/main/examples/graphiql-cdn) | ||
to show how to use GraphiQL with [esm.sh](https://esm.sh). | ||
|
||
### How to Update | ||
|
||
Follow the step-by-step guide in our | ||
[GraphiQL 4 migration documentation](https://github.com/graphql/graphiql/blob/main/docs/migration/graphiql-4.0.0.md). | ||
|
||
## What's Next? | ||
|
||
The development of **GraphiQL 5** is almost complete! You can checkout the last | ||
[Live Preview](https://deploy-preview-3234--graphiql-test.netlify.app). | ||
|
||
The official release is just around the corner — arriving later **this month**! | ||
|
||
## Stay Connected | ||
|
||
Follow me, **Dima Machina**, on [𝕏](https://x.com/dimaMachina_) and | ||
[GitHub](https://github.com/dimaMachina) to stay up to date with the latest | ||
updates! |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried a few queries and got errors:
produces error:
Similarly:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://discord.com/channels/625400653321076807/862957469155721236/1378406038382055474