Jaen

The console message clearly says what the error is, a history entry with the domain `192.168.1.81` can not be created when the document is loaded from domain `listen.localhost`. The domain...

Well, all I can suggest is using a debugger to set some break/watchpoints in https://github.com/TanStack/router/blob/21ce1351e5e88d89d8d8924666c4f97251da89ef/packages/history/src/index.ts to figure out how the invalid URL is generated.

This bug can theoretically cause infinite loops via the hover re-mount – in case a component instantiates their `` subcomponents **after** the initial mount (which would cause their hover to...

I'm sorry, but that's not really a solution? I don't think this should be closed? Are you saying there's **no way** to store links separately in a type safe way?...

Everything that's in `ToOptions`, including parameters. Anything that can be passed to both `useNavigate()` and `useLinkProps()`. The example does demonstrate that at least `UseLinkPropsOptions` is usable as a stand-alone type...

I would actually be happy with just a single function that can make a literal turn into _any one (pick what you like best)_ of the `*Options` types, since that's...

Clearly, eg. `ToOptions` should theoretically be passable to both `useNavigate` and `useLinkProps`, since both functions work with anything that practically conforms to that type. Any other behaviour would be a...

As a practical use case, a very simple and common example would be eg. in a design system, where you would have a component wrapping a link: ```typescript function MyLinkLike({...

@schiller-manuel I believe this is still a valid issue/problem (so this shouldn't be closed?) Design systems often use generic link representations. Here's my current "implementation" that "works": ```typescript export function...

Yeah, this is basically the same as #1194. I proposed contributing a solution but there was no response from the maintainers at that time. Here's the workaround I use currently:...