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.
using tanstacks context which has been nice. Not sure it that would have been quite possible that way in remix either.
This is a larger side project, so it’s a great candidate to explore its viability.
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
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 🙈🙈
Should mention this is a 2 step process. Migrating to tanstack router first, then eventually using it as a project to migrate to start.
Perfect timing - like 75% done migrating a remix spa app to tanstack router, looking forward to iterating on it once you got something posted! 🤘
You mean something like this, hey? Agreed, it’s a solid solution and probably what I will use.
Tbf, what I m looking for is achievable with just tanstack router loader. It would just feel ✨ delightful ✨declaring the query once and using its results across loader and component.
@tkdodo.eu @tannerlinsley.com hear me out… one thing I don’t “love” is that I need to call postQueryOptions(postId) twice. It’s fine - It makes sense, but I wished I could just “reuse” the same call. Maybe this is crazy, but do you think an API like this be possible? In query+router?
