test(react-router): reproducer starter for #2255

[SeanCassiere]

Important

These reproductions need to be corrected to match the expected route tree and the content to be displayed on the screen.

Starting for the reproductions for #2255

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f11d3de. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

🟥 Failed Commands
nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3

✅ Successfully ran 1 target

• nx run-many --target=build --exclude=examples/**

---

Sent with 💌 from NxCloud.

[pkg-pr-new]

Open in Stackblitz

More templates

• tanstack-router-react-example-authenticated-routes
• tanstack-router-react-example-basic
• tanstack-router-react-example-basic-default-search-params
• tanstack-router-react-example-basic-file-based
• tanstack-router-react-example-basic-file-based-codesplitting
• tanstack-router-react-example-react-query
• tanstack-router-react-example-basic-react-query-file-based
• tanstack-router-react-example-basic-ssr-file-based
• tanstack-router-react-example-basic-ssr-streaming-file-based
• tanstack-router-react-example-deferred-data
• tanstack-router-react-example-kitchen-sink
• tanstack-router-react-example-kitchen-sink-file-based
• tanstack-router-react-example-kitchen-sink-react-query
• tanstack-router-react-example-kitchen-sink-react-query-file-based
• tanstack-router-react-example-large-file-based
• tanstack-router-react-example-location-masking
• tanstack-router-react-example-navigation-blocking
• tanstack-router-react-example-quickstart
• tanstack-router-react-example-quickstart-file-based
• tanstack-router-react-example-quickstart-rspack-file-based
• tanstack-router-react-example-quickstart-webpack-file-based
• tanstack-router-search-validator-adapters
• tanstack-router-react-example-scroll-restoration
• tanstack-router-example-react-start-basic
• tanstack-router-example-react-start-basic-auth
• tanstack-router-example-react-start-basic-counter
• tanstack-router-example-react-start-basic-rsc
• tanstack-router-example-react-start-basic-react-query
• tanstack-router-example-react-start-clerk-basic
• tanstack-router-example-react-start-trello-trellaux
• tanstack-router-react-example-with-framer-motion
• tanstack-router-example-react-start-trellaux
• tanstack-router-react-example-with-trpc-react-query
• tanstack-router-react-example-with-trpc

@tanstack/history

pnpm add https://pkg.pr.new/@tanstack/history@2262

@tanstack/react-cross-context

pnpm add https://pkg.pr.new/@tanstack/react-cross-context@2262

@tanstack/react-router

pnpm add https://pkg.pr.new/@tanstack/react-router@2262

@tanstack/react-router-with-query

pnpm add https://pkg.pr.new/@tanstack/react-router-with-query@2262

@tanstack/router-arktype-adapter

pnpm add https://pkg.pr.new/@tanstack/router-arktype-adapter@2262

@tanstack/router-cli

pnpm add https://pkg.pr.new/@tanstack/router-cli@2262

@tanstack/router-devtools

pnpm add https://pkg.pr.new/@tanstack/router-devtools@2262

@tanstack/router-generator

pnpm add https://pkg.pr.new/@tanstack/router-generator@2262

@tanstack/router-plugin

pnpm add https://pkg.pr.new/@tanstack/router-plugin@2262

@tanstack/router-valibot-adapter

pnpm add https://pkg.pr.new/@tanstack/router-valibot-adapter@2262

@tanstack/router-vite-plugin

pnpm add https://pkg.pr.new/@tanstack/router-vite-plugin@2262

@tanstack/router-zod-adapter

pnpm add https://pkg.pr.new/@tanstack/router-zod-adapter@2262

@tanstack/start

pnpm add https://pkg.pr.new/@tanstack/start@2262

@tanstack/start-vite-plugin

pnpm add https://pkg.pr.new/@tanstack/start-vite-plugin@2262

commit: f11d3de

[SeanCassiere]

Currently, we've identified 3 scenarios that need resolution.

1. /about route with an async loader where this is thrown notFound()

<root.NotFoundComponent />

2. /about route with a non-async loader where this is thrown notFound()

<root.Component>
  <@tanstack/react-router->DefaultGlobalNotFound />
</root.Component>

3. /route-that-does-not-exist

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

2 definitely shouldn't be happening since it should be traversing up the route-tree to select the notFoundComponent.