Describe the bug#
If you throw notFound() in a loader after a short delay (e.g. when awaiting a request), the parent routes stay forever stuck in "pending" state.
This behaviour does not happen if the loader promise resolves very quick, e.g. within 100ms.
Simplest reproduction:
export const Route = createFileRoute('/posts/$postId')({
loader: async ({ params }) => {
try {
await new Promise((resolve, reject) => {
setTimeout(() => {
reject();
}, 1000);
});
} catch (err) {
throw notFound();
}
},
notFoundComponent: () => <div>Post not found</div>,
});
Your Example Website or App#
https://stackblitz.com/edit/tanstack-router-jc3pyp?file=src%2Froutes%2Findex.tsx
Steps to Reproduce the Bug or Issue#
- Go to
/posts/whatever in Stackblitz (posts.$postId.tsx)
Expected behavior#
A "Not found message"
Actual behavior#
The matched root route is stuck in a pending state according to the dev tools, the final route correctly has "not found" state.
This causes the page to never load.
Platform#
- OS: macOS
- Browser: Arc (Chrome)
- Version: 1.47
Additional context#
No response
@tannerlinsley This is currently very broken, where the router gets forever stuck in a pending state when
throw notFound()in any asyncloaderorbeforeLoad. Latest TSR version (v1.40.0)Simplest repro (updated Stackblitz):