Using middleware causes route matching to break after updating from v7.9.1 to v7.9.2

[ceisele-r]

Reproduction

1. Go to https://codesandbox.io/p/sandbox/react-router-v7-sy3yht
2. View the Chrome Devtools for the preview stating {status: 404, statusText: 'Not Found', internal: true, data: 'Error: No route matches URL "/"', error: Error}
3. Comment the line middleware: [anyMiddleware], out so no middleware is applied
4. Reload the page -> Route matching works

System Info

System:
    OS: Windows 11 10.0.22631
    CPU: (22) x64 Intel(R) Core(TM) Ultra 9 185H
    Memory: 33.11 GB / 63.45 GB
  Binaries:
    Node: 22.20.0 - C:\Program Files\nodejs\node.EXE
    npm: 11.6.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 10.15.1 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Chromium (140.0.3485.54)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    react-router: ^7.9.2 => 7.9.2
    vite: ^7.1.7 => 7.1.7

However, seems unrelated to the specific system as it is reproducible in the CodeSandbox.

Used Package Manager

npm

Expected Behavior

Route matching also works as before in v7.9.1 when using a middleware.

Actual Behavior

Route matching fails for all routes after updating from v7.9.1 to v7.9.2 without changing any other code:

{status: 404, statusText: 'Not Found', internal: true, data: 'Error: No route matches URL "/"', error: Error}

[timdorr]

It looks like this is caused by #14348.

You can workaround this by adding a dummy loader: loader: () => {},

[brophdawg11]

oops - yeah this is a regression in the no-loader case 😕. - I'll get this fixed in #14393 and should be able to have a patch out later today.

[github-actions]

🤖 Hello there,

We just published version 7.9.3-pre.0 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!

[github-actions]

🤖 Hello there,

We just published version 7.9.3 which involves this issue. If you'd like to take it for a test run please try it out and let us know what you think!

Thanks!