You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you throw notFound() in beforeLoad in index.tsx, it will not render its notFoundComponent. It will however render __root.tsx notFoundComponent if it is set, but there will be a CSS flicker of styles. Full repo here:
Clone the GitHub project and run pnpm dev
index.tsx will render a white page
Uncomment the notFoundComponent from __root.tsx
index.tsx will now render __root.tsx's notFoundComponent, and the background color will flicker on page refresh
Expected behavior
beforeLoad throw notFound() should render the route's own notFoundComponent, and fallback with "fuzzy" mode.
Docs were recently updated to reflect this. See here. Not sure about the styles flicker you're seeing though.
⚠️ Throwing a notFound error in a beforeLoad method will always trigger the __root notFoundComponent. Since beforeLoad methods are run prior to the route loader methods, there is no guarantee that any required data for layouts have successfully loaded before the error is thrown.
Docs were recently updated to reflect this. See here. Not sure about the styles flicker you're seeing though.
⚠️ Throwing a notFound error in a beforeLoad method will always trigger the __root notFoundComponent. Since beforeLoad methods are run prior to the route loader methods, there is no guarantee that any required data for layouts have successfully loaded before the error is thrown.
There will be a FOUC if you refresh the route that threw notFound() in beforeLoad, or enter the route directly from the address bar. There is however no FOUC for client side navigations to the route. Not sure if it is tailwind related or not.
Activity
roduyemi commentedon Oct 27, 2025
Docs were recently updated to reflect this. See here. Not sure about the styles flicker you're seeing though.
jasperteo commentedon Nov 4, 2025
There will be a FOUC if you refresh the route that threw
notFound()inbeforeLoad, or enter the route directly from the address bar. There is however no FOUC for client side navigations to the route. Not sure if it is tailwind related or not.Pyakz commentedon Dec 21, 2025
up
schiller-manuel commentedon Mar 30, 2026
this has been fixed