I always split router/page logic from my actual features. This made migrating from remix (spa) to @tanstack.com router a breeze. A lot less non null assertions 🙈🙈 - ThreadSky

About ThreadSky

I always split router/page logic from my actual features. This made migrating from remix (spa) to @tanstack.com router a breeze. A lot less non null assertions 🙈🙈

1 / 2

Comments

azarkhish.com•176 days ago

Why not type safety of RR7 instead of full migration to TanStack?

itspatricku.bsky.social•176 days ago

Tbh I haven’t explored rr7 that much yet. I’ve been following tanstack router development for a while and it has been everything I wanted from a router. Rr4 wasn’t it, Rr5 wasn’t it, rr6 wasn’t, remix wasn’t it either. Fool me 4 times… haha

Also I’m pretty excited about what I see in tanstack start

itspatricku.bsky.social•176 days ago

This is a larger side project, so it’s a great candidate to explore its viability.

tannerlinsley.com•176 days ago

RR’s type safety is infinitely better than none at all, but still very young and leaves a lot to be desired. If you value types, use TSR.

jos.bsky.social•176 days ago

How does this look on routes that have loaders though?

itspatricku.bsky.social•176 days ago

I very much underutilized loaders in remix in this project so I can’t speak too much to the migration of them. That being said, loaders are great in tanstack. I also ended up rewriting and get rid of a handful of providers (e.g. a user provider) by leverages tanstacks context which has been sweet.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply