[graphiql] graphiql/plugin-explorer dependency graphiql-explorer has outdated peerDependencies

[wleese]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

graphiql/plugin-explorer dependency graphiql-explorer has outdated peerDependencies:

 "peerDependencies": {
   "graphql": "^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0",
   "react": "^15.6.0 || ^16.0.0",
   "react-dom": "^15.6.0 || ^16.0.0"
 }

Functionally it seems to work with react+react-dom 19.2.8 an graphql 17.0.2, however the npm warnings are obnoxious. :)

Expected Behavior

No response

Steps To Reproduce

With:

  "dependencies": {
    "@graphiql/plugin-explorer": "5.1.5",
    "graphiql": "5.4.0",
    "graphql": "17.0.2",
    "react": "19.2.8",
    "react-dom": "19.2.8"
  }

npm install

Environment

• react Version: 19.2.8
• graphql Version: 17.0.2

Anything else?

No response

[trevor-scheer]

If it's an option for you, would you consider giving the GraphiQL v6 beta a try? We're shipping a new Query Builder plugin @graphiql/plugin-query-builder which supersedes the Explorer plugin. I won't speak for other maintainers (I'm the only active one as of late) but I don't intend to maintain the Explorer plugin going forward; the v6 release will formally deprecate it. I wouldn't be opposed to critical/security fixes but probably nothing beyond that.

If you do try out v6, I'd love to hear your feedback and how the migration went. It shouldn't be a huge lift. The v6 migration guide is still a WIP but should be sufficient, especially if you're able to just point an LLM at it.
https://github.com/graphql/graphiql/pull/4228/changes#diff-768415342138dfcf2baf3afac9a5a10f58146f235be97ef900fd2cc0bd262817