Maybe, but I stopped using React Router many major versions ago. I have never, in my entire career, seen a library change (in large, completely non-backward-compatible ways) as many times as React Router. It's like the author just decides to do things completely differently in every new version for fun.
Maybe he finally guessed right on the 7th time, but I just can't imagine building my site around a tool that changes it's entire paradigm annually.
Designing for bundlers/compilers/typegen (and any pre-runtime static analysis) leads to poor api design that eventually pollutes the entire system
Is this in reference to React Router v7 that just shipped?
> We're simply struggling to build something that feels like React did when we first found it.
> That's why Remix is moving on from React
> Remix v3 is a completely new thing. It's our fresh take on simplified web development with its own rendering abstraction in place of React.
> Inspired by all the great tech before it (LAMP, Rails, Sinatra, Express, React, and more), we want to build the absolute best thing we know how to build with today's capable web platform.