consider switching routers from react-router to tanstack's router
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10
- Forks
- 5
- Avg merge
- 2h 41m
- Merged PRs (30d)
- 66
Description
Most of the worst code in the app relates to the router (eg #261), which continues to disappoint. As far as I can tell, react-router is moving in the direction of primarily supporting remix's ssr solution and the api has suffered as a result. Additionally, the type declarations are the weakest part of the app. I have no experience with tanstack's router, but it can't be worse.
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 reading issue #261 and the TanStack Router comparison linked in this issue. Review how routing and type declarations are currently used in the app before defining the migration scope. Done would require an agreed router direction and a complete, working replacement rather than an isolated edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100