Root route component is rendered for non-matching-route path but not for missing resource #2255

Activity

1. SeanCassiere

   added

   information neededFurther information is requestedFurther information is requested

   on Sep 3, 2024
2. SeanCassiere commented on Sep 3, 2024

   

   SeanCassiere

   on Sep 3, 2024

   Last edited by SeanCassiere

   Member

   More actions

   Please attach a valid minimal reproduction showing off the issue in question.

   Edit: Link to a stackblitz starter - https://stackblitz.com/github/tanstack/router/tree/main/examples/react/quickstart-file-based
3. lo1tuma commented on Sep 4, 2024

   

   lo1tuma

   on Sep 4, 2024

   ContributorAuthor

   More actions

   I’ve used the quickstart-code-based as a template. Here is the adjusted version that demonstrates the issue https://stackblitz.com/edit/github-bfat87?file=src%2Fmain.tsx

   Steps to reproduce:

   • In the browser when you are on the home page
   • click the "About" link
   • -> you see the not found page without menu
   • click on "back to home"
   • click on "Non-Existing Page" link in the menu
   • -> you will see the not-found page but this time with menu
4. SeanCassiere

   added

   bugSomething isn't workingSomething isn't working

   and removed

   information neededFurther information is requestedFurther information is requested

   on Sep 4, 2024
5. SeanCassiere commented on Sep 4, 2024

   

   SeanCassiere

   on Sep 4, 2024

   Member

   More actions

   Throwing a notFound error in a route's loader, outputs the following route-tree.

   <root.NotFoundComponent />
   

   Navigating to a route that DOES NOT EXISTS in the route-tree, results in this route-tree.

   <root.Component>
     <root.NotFoundComponent />
   </root.Component>
   

   Note that this configuration does not have a defaultNotFoundComponent.

   By default the Router has the setting of notFoundMode: 'fuzzy', where the router traverses up the tree until it finds the nearest notFoundComponent (which in this case would be the one configured on the root route).
6. lo1tuma commented on Sep 4, 2024

   

   lo1tuma

   on Sep 4, 2024

   ContributorAuthor

   More actions

   Thanks for the further investigation and writing a test-case @SeanCassiere. I haven’t thought about the non-async case.

   My expected behavior would be that the behavior is consistent across all scenarios, so either the NotFoundComponent should be always wrapped or never.

   👍React with 👍1Reacted by nikuscs
7. LadyBluenotes commented on Jul 11, 2026

   

   LadyBluenotes

   on Jul 11, 2026

   Member

   More actions

   @pupuking723, would you mind taking a look and letting us know what you find?

   A fix would be welcome if it still reproduces. Please keep it focused on making the root layout consistent between an unmatched path and a loader-thrown notFound(), with regression coverage for both paths if it is still present :)
8. LadyBluenotes commented on Jul 11, 2026

   

   LadyBluenotes

   on Jul 11, 2026

   Member

   More actions

   Thanks for checking @pupuking723!
9. LadyBluenotes

   closed this as completedon Jul 11, 2026