Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Redirects cause root route loader invocation but root route component does not receive loader data
See original GitHub issueWhat version of Remix are you using?
1.5.1
Steps to Reproduce
A repo with a minimal reproduction is available here: https://github.com/jangerhofer/remixRootRouteRedirectReproduction along with some directions.
Expected Behavior
I expect that a server-side redirect (whether performance only once or multiple times) would cause a fresh root route loader function invocation and that the (serialized) value returned from the loader would be made available to the root route component via the useLoaderData hook.
Actual Behavior
Instead, I see only the invocation the root route loader; the useLoaderData hook’s value remains an empty object despite the loader returning data.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Definitely sounds like multi-redirect is the problem here. I’m pretty sure our new code over in React Router doesn’t do this. @brophdawg11 you mind looking into this one, fixing in Remix and verifying we have a test for it in React Router?
Should be able to make a test case out of the repo² pretty easily (get it? reproduction repository, the repo squared?! … yeah it’s early).
Closed by #3460