RIP React Router?

So hyped for you Tanner. Tanstack Router is a HUGE release and it's going to change how we think about our routes forever.

Huge shoutout Mir for killing it on this edit 🙏

[tannerlinsley]

Wow LOVE THIS. What’s even cooler is that since you recorded this, the syntax is even better and more type safe! 🤯 and to the point of SSR, support is already there. We’re currently working on extending that support to something that would allow you to build your own framework and even a crazy cool opt-in file-based routing utility that translates into the same code-driven type safe route defs Theo showed off here. The future is bright!

[Shri]

Tanstack Router is just mind blowing! I hope Remix takes Tanner into the team and bring in all the Typescript juiciness of Tanstack Router to Remix as well. It will be an amazing combination!

[volimsir]

Similar to react-query, I wouldn't have this in my next app by default - rather only if I needed it.
File based routing is simple enough, just works out of the box, and it's one less thing I need to worry about when building stuff. Unless you need query params for many pages, it just doesn't seem worth it for now. But it's still in beta, and next support isn't there yet, so let's see what happens in the future. It's definitely cool to see type based routing like this. Although it does feel like we're just going back in time.

[underflowexception]

All these new frameworks and libraries are great but they change too rapidly to actually implement them in production at work imo. Fun for personal projects though.

[dinckelman]

This is super fucking exciting. We've been riding that wave of "i hope it works" for entirely too long. With this kind of stuff, you want, and even NEED to know exactly what you're getting, so i'm all for type safety throughout the whole stack. For a typescript dev, this is a great time to exist. People are finally stopping treating TS like a second-class citizen

[lukasmolcic]

I have a feeling we are moving more and more back to patterns similar to MVC in traditional BE based web apps

[petarkolev]

Wow, amazing! Thanks for the awesome demonstration, Theo!

[zenpool]

tanstack already have the parts to make a next.js/remix competitor! we just need a server-side/ssr solution

[francoisguezengar]

Wow, it's like the angular router. Do you know if you can guard the page and redirect based on some conditions?

[runonce]

Thanks for the vid. Really neat stuff, specially the TS support. Although I do think that file based routing (i. e. Next.js, Remix) and nested routes were also some major improvements in frontend routing landscape.

[Affax]

Tanstack always impresses me more and more.
Recently moved to Tanstack Query and it made my life so much better.
I mostly use NextJS (tho, most of my apps are SPAs), so might be time to just move to better pastures and start using this.

[AlonMiz]

Cool. Btw for nesting params there's a reasonable lib called rison. Supporting json arrays boolean etc. And it's much more readable than encoding a regular json string

[keith-is-mad]

Accidentally we've made just about the same typesafe thing inhouse a few years ago - only with object configs and a few more generic wrapper functions.
The same story was with redux-toolkit when there was no such thing as redux-toolkit. And also with tables and forms... though it seems nobody have solved the damn tables and forms yet.
It's like a fermi paradox. Every time i'm thinking "why it's not a solved problem yet", i'm reminding myself that there might be countless inhouse devs that are asking the same exact question.
Most of the time we just can't share the results.

[ciarancurley]

Thanks a lot Tanner and Theo for this. I'm knee deep in a refactor of the app at my new job, currently moving old loading boilerplate api code to use Tanstack Query, and a routing shake up will be next, alongsite the eventual TypeScript migration. Will keep an eye on the Github and Discord.

[EduardoSanchez-unhh]

React is finally catching up with Angular.

[phendan]

The one thing I really miss having migrated from Vue to React is the way you can basically have a middleware stack in front of a route to check things like auth state and only load the actual component once you're sure it makes sense to load it. Next still doesn't seem to have a way to do this properly, and it's honestly kinda baffling to me.

[kelvindimson]

Is this not what angular had been doing ?? 🤔

[zyzlol]

nice to see deep linking support out of the box. it's missing in too many apps

[MonamaTV]

"Routing has just changed forever. That's a bold statement, but Tanner is a bold person"
I think this is a cool opening line.

[appuser]

this looks AMAZING. Can't wait for this or the concept to catch up outside my own projects :)