[Bug]: Using hash with lazy component results in an empty page on initial load

[erism]

What version of React Router are you using?

6.11.1

Steps to Reproduce

Add any hash value to route that uses lazy component and refresh the page.

Example codesandbox

Expected Behavior

Using hash shouldn't cause route matching problem.

Actual Behavior

It results in an empty page with console warning:
Matched leaf route at location "/path#hash" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.

• Navigation with hash doesn't cause this problem; it only occurs on initial load.
• It's broken after 6.11.1 upgrade. 6.11.0 works normally.

[brophdawg11]

Thanks for the reproduction! This looks like a side effect of #10408 since it's not treating initial page loads with a hash as a "same hash" navigation - we'll get this fixed up in a patch release soon!

[brophdawg11]

This is fixed by #10493 and will be available once 6.11.2 is released 👍

[github-actions]

🤖 Hello there,

We just published version 6.11.2-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 6.11.2 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!