#reactlocation search results

Does this @tan_stack/#ReactLocation loading return stale data while revalidating when used in conjunction with @trpcio's useContext? 🧐 cc: @alexdotjs & @tannerlinsley

Have anyone used #reactlocation with @storybookjs ? Would love to see some examples /cc @tannerlinsley

Recently discovered #ReactLocation and replaced #ReactRouter in an app I'm working on. Really happy with all the much-needed extra features.

I put the "React" in #ReactLocation.... so guess I could take it out too, right? 😏

Considering removing the async features from #ReactLocation and doubling down on its powerful search param features. React Router will likely fill the async gap pretty well for most people. The async stuff can also feel like a maintenance shackle.. So what is it, prune or tune?

😃 Joining us for #StateOfReact - the creator of #ReactQuery, #ReactLocation and many more #reactjs libraries! ☀️ Welcome @tannerlinsley!! Sign up to hear from him and other React experts! 👇 buff.ly/2OcpSYy

📦 Generouted is now available on @npmjs! Generated routes for #ReactLocation and @vitejs 📂 File-based routing @nextjs inspired 🚀 Code-splitting and pre-loading ⚡︎ Data loaders for routes and layouts 💿 Nested layouts @remix inspired ➡️ github.com/oedotme/genero… @tan_stack

#ReactLocation's documentation search is finally working again. Search away! react-location.tanstack.com

@tan_stack #ReactLocation Is it possible to change the specification so that the root loader operates every time the search parameter is changed? I understand github.com/TanStack/react…. However, if the data acquisition process can be summarized by the root loader, >>

#ReactLocation があれば、nextjsもremixも要らなそうやな。。 cra+ReactRouterだとコンポーネントロード前の事前フェッチが難しかったから、dataloader機能はありがたい。 まあ、ReactQuery大好きっ子なので、ReactLocationを過大評価してるかもですが。これから使い込んで結論だします😅

#ReactLocation just got a nice new patch release: - fix: Routes with 2+ nesting levels states now properly cascade nested pending states - fix: Routes with async elements but no loader/import can now trigger a pending state Route on! 👍 react-location.tanstack.com

What I'd consider the perfect @reactjs stack today: 🧩 Components: @MUI_hq 🛣️ Routing: #ReactLocation 📦 Query: @apollographql (haven't tested #ReactQuery yet 🙊) 🏗️ GQL Typing: @TheGuildDev 🪟 Tables: #ReactTable 🌍 Intl: #ReactIntl Happy to discuss why 👇

Just tested #ReactLocation from @tannerlinsley. This is brilliant, makes you want to use query params for everything, which is ideal for users.

This is now even easier to do with #ReactLocation's with the new `stringifySearchWith` and `parseSearchWith` utilities! 🎉

These questions are running through my head *all day* and have become indispensable, especially with the work I do on @nozzleio. @tan_stack's #ReactLocation isn't perfect, but I feel like it has pretty good answers and solutions to all of these questions.

Search param filters are relatively undocumented and unadvertised in #ReactLocation but I am convinced they are easily the most powerful and also my favorite feature, even beyond all of the async stuff. Having 100% control over search params at the url generation level is 🔥🌶️

#ReactLocation v3.5.0: - `hash: true` allows url hash retention on navigation destinations - Initial location state is verified to include any searchFilter logic and replaced in a layout effect if it produces different locations. github.com/TanStack/react…

#ReactLocation's npm packages are now located under the new tanstack npm namespace! - @ tanstack/react-location - @ tanstack/react-location-devtools - Etc.. One more repo done, several more to go!

A new patch version of #ReactLocation is now available which is worth mentioning here. Mainly, we improved the way cascading loading-vs-pending states work, so you can now render synchronous wrapper elements who's child routes also suspend until resolved or pendingMs hits.

Nope. It's our own tree component. We also use it in #ReactQuery and #ReactLocation devtools.

So... this totally works. Is #ReactLocation SSR really this simple?

Does this @tan_stack/#ReactLocation loading return stale data while revalidating when used in conjunction with @trpcio's useContext? 🧐 cc: @alexdotjs & @tannerlinsley

Wow, I'm really stoked on the latest changes I just made to #ReactLocation. Preloading routes just became as easy as using useNavigate(), because obviously prefetching routes needs to be absolute/relative path + hash + search-param aware 🎉

This also quietly demonstrates #ReactLocation's nested routing support. The Router/routes for this example looks like this currently:

Did I mention #ReactLocation routes have some nifty callback functions similar to `useEffect`? You can run isolated side-effects when routes move between active, transitioned and inactive states. 😍 Reminds me of XState's enter/exit events, but for your routes!

📦 Generouted is now available on @npmjs! Generated routes for #ReactLocation and @vitejs 📂 File-based routing @nextjs inspired 🚀 Code-splitting and pre-loading ⚡︎ Data loaders for routes and layouts 💿 Nested layouts @remix inspired ➡️ github.com/oedotme/genero… @tan_stack

Wish I was working on #ReactLocation, but at least things are gettin’ supes lit up here.

😃 Joining us for #StateOfReact - the creator of #ReactQuery, #ReactLocation and many more #reactjs libraries! ☀️ Welcome @tannerlinsley!! Sign up to hear from him and other React experts! 👇 buff.ly/2OcpSYy

Documenting #ReactLocation right now and forgot to mention that you can set loader maxAge like 5 different ways including from the loader function itself. So like, wanna use that max-age Response header?

Writing more docs for #ReactLocation with @GitHubCopilot on and I am doing quadruple takes at the recommendations. Did co-pilot make this up? Did it grab this straight out of React Router's docs? 🤔 WHERE ARE YOU GETTING THIS!!! co-pilot: "billions of lines of public code"