[graphiql] graphiql/plugin-explorer dependency graphiql-explorer has outdated peerDependencies
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.9k
- Avg merge
- 22h 45m
- Merged PRs (30d)
- 70
Description
### Is there an existing issue for this?
- [x] 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_
Contributor guide
Research direction
Locate the graphiql-explorer package metadata used by @graphiql/plugin-explorer and compare its peerDependencies with the React, react-dom, and GraphQL versions in the report. Verify the dependency metadata against the provided npm install reproduction, and consider the work done when installation no longer emits the reported peer-dependency warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, react
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100