GraphiQL Next path proposal

[dimaMachina]

GraphiQL Next path proposal

Hi, I am one of the current GraphiQL maintainers, and I’m excited to share the future GraphiQL 4 and 5 proposal, which will introduce:

• Migration to Zustand for state management (replacing React context)
• Migration to Monaco-Editor/Monaco-GraphQL (replacing CodeMirror)

These versions will be released sequentially. Below is the detailed roadmap:

GraphiQL 3.x (GraphiQL x Vite/React 19)

• Migrate to Vite (Done in #3826, pending release)
• Compile GraphiQL source code (Done in #3826, pending release)
• Support React 19 #3876 [graphiql] Update graphiql-react to support React 19 #3850
  • Upgrade @headless/react to v2 in graphiql-react

GraphiQL 4 (GraphiQL x Zustand)

• New tab design (Merged in v4 alpha, visible in GraphQL Hive)
• Extract plugins into separate packages (issue #2904):
  • Explorer plugin
  • History plugin
• Migrate from React context to Zustand (issue #2904)
• Ensure all tests pass

GraphiQL 5 (GraphiQL x Monaco)

• Migrate to Monaco-Editor/Monaco-GraphQL (I did POC in 2023 in #3234)
• Ensure all tests pass

---

Feel free to ask any relevant questions. The GraphQL TSC have indicated that if we're all in agreement they will approve my grant to work on this.

Let's get this built!

Dimitri

[acao]

Looks good to me, just like we decided on last year. Let me know if you need any help reviewing anything!

This rewrite for v4 branch takes care of the entire core zustand state, the only bug I had was with persistence (if you comment out the persist middleware it works great )

thanks, @dimaMachina !