to allows the string type

[nstepien]

Which project does this relate to?

Router

Describe the bug

As the title says, to accepts the string type, meaning that these examples will be "valid":

router.navigate({ to: `/posts?filter=${filter}` });

<Link to={`/posts?filter=${filter}`} />

Your Example Website or App

https://stackblitz.com/edit/github-vg75qp?file=src%2Fmain.tsx

Steps to Reproduce the Bug or Issue

1. Pass a value of type string to to

Expected behavior

The string type should not be accepted by to's type

Screenshots or Videos

No response

Platform

• OS: Windows
• Browser: Chrome
• Version: 130.0.6723.59

Additional context

I don't know if this is intentional, but it's making migrating away from another router more difficult as we can't automatically trust links/navigations.

[schiller-manuel]

we have been thinking about this. thanks for opening this issue to remind us :)

[swbtrifork]

My workaround for now seems to be to narrow the type manually by using as const satisfies LinkProps["to"];, but this was also an issue for me, especially in shared components.