fix: normalizeURL does not ensure path name starts with a /

[dargmuesli]

Environment

---

• Operating System: Linux
• Node Version: v16.20.0
• Package Manager: [email protected]

---

Reproduction

https://stackblitz.com/edit/stackblitz-starters-rbpv5q?file=index.mjs

Describe the bug

The example in the README does not work as specified.

Additional context

No response

Logs

No response

[pi0]

Hi. Can you please share the context of this issue and did you find any standards that specify a valid URL needs one trailing slash at least? (because browser URL, doesn'y do it, but URL constructor seems to add. i didn't check any standards yet)

[dargmuesli]

I just expected to happen what's written in the README of this project. I'm not sure about standards and thus am fine with changing the README too to reflect the actual behavior of ufo.

[Anoesj]

I agree the README should be updated, because normalizeURL does not ensure a leading slash if pathname is ''.

Had to add this in my own project:

const normalizedURL = normalizeURL(url);
const { host, pathname, search } = parseURL(normalizedURL);
const pathnameCleaned = pathname === '' ? '/' : pathname;

[pi0]

Docs updated in the meantime and for v2 it is likely this behavior changes (~>#208).

If v1 was not widely used, I would add it as a fix but this fix has potential of breaking some other cases.

(closing to track from one place for all side-effects in v2)