throwing notFound() in loader renders the defaultNotFoundComponent, even when a notFoundComponent exists in __root__

[anthonyma94]

Which project does this relate to?

Router

Describe the bug

When throwing notFound() in a loader function, the not found component is always the defaultNotFoundComponent, even when notFoundComponent is assigned in __root__. This applies even if you use notFound({ routeId: rootRouteId }).

Your Example Website or App

https://stackblitz.com/edit/github-51knrjza?file=src%2Froutes%2Fabout.tsx

Steps to Reproduce the Bug or Issue

Go to the about page.

Expected behavior

notFound should follow the default not found rules.

Screenshots or Videos

No response

Platform

• OS: WSL
• Browser: Firefox
• Version: 1.114.27

Additional context

No response

[kevincrossgrove]

+1

[schiller-manuel]

is this the same as #2255 ?

[anthonyma94]

Looks like it, is there an ETA on a fix?

EDIT: after further investigation, the issue is different. Mine is about the defaultNotFoundComponent appearing instead of root's notFoundComponent, even though the rest of the root layout is loaded. #2255 is the opposite, their root notFoundComponent is loaded while their root layout is not.

[maiermah]

+1 for me

[whoisandy]

+1 for me as well

[viclafouch]

+1

[LadyBluenotes]

Fixed on current main. I verified both bare and root-targeted loader notFound() calls now render the root route’s custom boundary while preserving the root layout.

The relevant boundary-resolution changes landed in PR #6811. If this still behaves differently on the latest version, please open a new issue with an updated reproduction, please!