Built-in support for native <a>

[kentcdodds]

With the new href utility, it seems like <Link/> doesn't really do much (shout-out to #13115 too btw). And if #10748 is supported, then the <NavLink/> wouldn't be necessary either.

It would be nice to in a hook like this and make native anchor elements work:

// Thanks Devon: https://twitter.com/devongovett/status/1672307153699471360
export function useLinkHandler() {
	const navigate = useNavigate()

	useEffect(() => {
		function onClick(event) {
			const link = event.target.closest('a')
			if (
				link &&
				link instanceof HTMLAnchorElement &&
				link.href &&
				(!link.target || link.target === '_self') &&
				link.origin === location.origin &&
				!link.hasAttribute('download') &&
				event.button === 0 && // left clicks only
				!event.metaKey && // open in new tab (mac)
				!event.ctrlKey && // open in new tab (windows)
				!event.altKey && // download
				!event.shiftKey &&
				!event.defaultPrevented
			) {
				event.preventDefault()
				navigate(link.pathname + link.search)
			}
		}

		document.addEventListener('click', onClick)
		return () => {
			document.removeEventListener('click', onClick)
		}
	}, [navigate])
}

[sergiodxa]

Would be nice if there's a way to tell the router to ignore a link, something like data-document

return (
  <>
    <a href={href("/safe/path")} data-document>This uses MPA-style navigation</a>
    <a href={href("/safe/path")}>This uses SPA-style navigation</a>
  </>
)

This would be required to keep reloadDocument support.

[kentcdodds]

I think <Link /> could be kept around for special cases like that (and prefetching etc). I mostly just want native <a> support for typical/simple cases.

[okalil]

What about the other Link properties? preventScrollReset, reloadDocument, state?
There are the relative paths too, if I'm not wrong in RR they are relative to the context where inside were rendered, not to the current url.

[kentcdodds]

As I said in response to @sergiodxa, I think Link should be kept around for those special use cases, but for typical use cases, supporting native <a> would be quite nice.