TTC
Theo's Typesafe Cult•8mo ago
BREAD

Best way to store data between routes

Is History API a good thing in terms of storing data between routes? What is the best tool to use for this purpose? I see that it stores some weird data when I reload the page instead of navigating to it on client-side At my job we are heavily using react-router and it's history API to pass data from route to route What is the approach with NextJS to achieve such thing? I was also thinking about some kind of global Context but I want simplest solution to create minimal maintenance burden
0 Replies
No replies yetBe the first to reply to this messageJoin
Want results from more Discord servers?
Add your server
More Posts
Proper way to handle api routes with GoHey, I'm just wondering what the correct way to handle API routes with Go is. Currently, I have a roSyntaxError: Cannot use import statement outside a module. t3 envHello, I am having an error while following the t3 env stack's documentation.which of this approach is better?1) ```js const { password, ...userWithoutPassword } = user; return userWithoutPassword ``` 2) ```jsWhy do I have to check if function is null inside an if?Hello everyone, sorry for the very generic question, but I can't seem to find an answer and I'm a bi