calling navigate with relative path url "../newpath" appends to current url

[chiefcll]

Describe the bug

Given I'm on a page
/show/home/fiction/333

and I call
const navigate = useNavigate();
navigate("../similar/333")

It redirects to /show/home/fiction/333/../similar/333

Your Example Website or App

None

Steps to Reproduce the Bug or Issue

Described above

Expected behavior

Expecting Router to support relative paths
It should redirect to /show/home/similar/333

Screenshots or Videos

No response

Platform

Mac + Chrome

Additional context

No response

[chiefcll]

I assume it's not supported...

Doesn't look like this is doing any logic to check for ../ or ./

[ryansolid]

Yeah we never implemented relative paths like that.

[chiefcll]

Are you planning on supporting this or should I go with absolute paths?

[ryansolid]

An update on this: on the 2.0 branch (next, 1.0.0-next.x), navigate(string) now resolves relative strings with URL semantics — the same way the browser resolves an href. So navigate("../similar/333") from /show/home/fiction/333 lands on /show/home/similar/333 instead of leaving literal .. segments in the URL. Bare strings resolve as siblings (navigate("c") from /a/b goes to /a/c), and ?/#-only strings keep the current path. Leading-/ paths are unchanged.

We aren't planning to change this in 0.x — there, relative navigation intentionally resolves against the matched route hierarchy rather than the URL, and changing it now would break existing apps that rely on that. The workaround for 0.x remains resolving the path yourself (e.g. via new URL(to, location.href)) before calling navigate.

Leaving this open until 2.0 ships as the resolution.