Top Tweets for #ReactLocation

almost 4 years ago

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

9

113

0

1

0

about 4 years ago

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?

3

6

0

This Dot Media

@ThisDotMedia

about 4 years ago

😃 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! 👇 https://t.co/gK9xkUYmcH

0

5

1

0

Omar Elhawary @oedotme

about 4 years ago

📦 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 ➡️ https://t.co/w4FCKjpp5a @tan_stack

oedotme's tweet photo. 📦 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

➡️ https://t.co/w4FCKjpp5a

@tan_stack https://t.co/DsAAORdghD

2

59

7

9

0

about 4 years ago

#ReactLocation's documentation search is finally working again. Search away! https://t.co/IepXwplhTK

0

31

5

1

0

over 4 years ago

#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! 👍 https://t.co/IepXwplhTK

1

23

3

1

0

Nicolas @NicolasKa3

over 4 years ago

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 👇

1

8

1

2

0

Nicolas @NicolasKa3

over 4 years ago

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

2

18

3

1

0

over 4 years ago

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

over 4 years ago

@ScriptedAlchemy What that *really* means is that the resulting URL is almost exactly the same length as the original JSON syntax that it represents. Pretty incredible.

tannerlinsley's tweet photo. @ScriptedAlchemy What that *really* means is that the resulting URL is almost exactly the same length as the original JSON syntax that it represents. Pretty incredible. https://t.co/YngmrkpcMT

1

10

0

1

0

3

18

4

1

0

over 4 years ago

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.

3

7

0

over 4 years ago

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 🔥🌶️

4

40

3

2

0

over 4 years ago

#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. https://t.co/pxcjJ3p7Oe

1

22

0

over 4 years ago

#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!

0

35

2

0

over 4 years ago

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.

0

20

1

0