Melvin Valster
Melvin Valster
@stefanpenner @elucid @rickharrison I too wonder about the status of this PR/repository. This particular PR is 14 months old now. How's the support?
Seems I encountered similar behaviour in * #1795
Yes I think it's a bug. The docs explicitly state: > You, the developer must throw a not-found error when a resource cannot be found. This can be done in...
@lvl99 After an hour or so of chasing the MODULE_NOT_FOUND error I've also came to the conclusion it's due to this package. Wish they wouldn't pin the `npm` version down...
What's the status of this nowadays @JonathanPorta ? :)
Just ran into this, can confirm this confusing behaviour is still around.
I found this in `v1.34.9` as well, causing `context` to become `undefined` if the route that throws the redirect has search params that are being validated through `validateSearch`, and the...
Also noticed that adding this makes the app a lot more snappy, especially since we perform a lot of middleware/guard checks in `beforeLoad()` which takes almost no time. The default...
@tannerlinsley This is currently very broken, where the router gets forever stuck in a pending state when `throw notFound()` in any async `loader` or `beforeLoad`. Latest TSR version (`v1.40.0`) Simplest...
@schiller-manuel Would be amazing if you could confirm this use-case is also solved by #1907 😍