DefinitelyTyped / DefinitelyTyped/DefinitelyTyped
Bug: react was upgraded to react18, but types/react version is not limited in types/react-route, resulting in type compatibility error
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 51.4k
- Forks
- 30.4k
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 108
Description
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the dependency declarations for @types/react-router-dom and compare them with @types/react-dom. Run yarn install and the project build to reproduce the React 17/18 type mismatch. Done means the React type dependency stays compatible with React 17 and the project compiles successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100