[TheHypnoo]

Summary

new URL() kept . and .. path segments in pathname/href (https://x/a/b/../c reported /a/b/../c, Node reports /a/c), and the same parse pass was missing the rest of the WHATWG special-scheme shape — \ separators, the optional //, file: slash states and drive letters. Both land together because they are one rule family: the path/authority states of the standard's parser.

Changes

• crates/perry-runtime/src/url/parse.rs
  • normalize_hierarchical_path: WHATWG path-state rules over a path string. Single-dot segments (., %2e) are dropped, double-dot (.., .%2e, %2e., %2e%2e) shorten the path, a dot segment in final position appends an empty segment (/a/.. → /, /a/b/.. → /a/), empty segments from a // run survive (//a/../b → //b), a segment that merely contains a dot is untouched (/a/.../b). file:-only: a Windows drive letter canonicalizes to : (C| → C:) and a path that is only a drive letter is never shortened (file:///C:/.. → /C:/).
  • parse_url applies it to the hierarchical branches only; opaque paths (mailto:, data:) keep their text.
  • Special-scheme shape: \ folds to / before the host is read (query/fragment keep theirs, a non-special path keeps them, a non-special host may not contain one); a special scheme is always hierarchical with an optional // and a skipped separator run (https:x, https:/x, https:///x host x); file: keeps its own slash states (extra separators are path, empty host allowed) and now canonicalizes its host like any other special scheme (file://SERVER/x → server).
  • is_valid_absolute_url mirrors the parser instead of requiring a literal //, and no longer rejects an opaque URL with nothing after the colon (mailto: is valid, as in Node).
• crates/perry-runtime/src/url/url_class.rs: js_url_set_pathname runs the same states (assignment clears the path and re-parses the value); the duplicated is_special_url_scheme now lives in parse.rs only.
• test-parity/node-suite/url/url/dot-segments.ts and .../backslash-and-separators.ts: new node-parity cases.
• changelog.d/12864-url-dot-segments.md: changelog fragment.

Known divergences found while probing but not addressed here (separate defects, candidates for their own issues): the constructor does not apply the WHATWG path percent-encode set (/a b<c vs Node /a%20b%3Cc), url.domainToASCII("a/b") returns a/b where Node returns a, and the pathname setter stores a value on an opaque URL where Node ignores the assignment.

Related issue

Closes #12864

Test plan

• cargo build --release -p perry -p perry-runtime-static -p perry-stdlib-static — clean (the perry compile link surface used for the runs below, plus scripts/gc_call_effects/sidecars.sh target/release)
• PERRY_SKIP_BUILD=1 ./run_parity_tests.sh --suite node-suite --module url — 69/69 PASS (67 pre-existing + the 2 new cases), no previously-passing case changed
• New cases print byte-identical output to node --experimental-strip-types (diff empty, 64 and 43 lines)
• The issue's reproduction: perry compile prints 0 /a/c /c, node prints 0 /a/c /c
• Full cargo test --workspace … — not run locally (crate-scoped tests plus the module parity suite instead); CI's cargo-test job is the backstop
• (if user-facing) Added the node-parity cases under test-parity/node-suite/url/url/ — the url module's own suite, which is where Node-core module behavior is pinned
• (if CLI / stdlib / runtime API changed) Updated docs/src/ — no dedicated node:url page exists to update; the behavior is pinned by the node-parity suite
• (if touching a platform UI backend) n/a
• cargo fmt --check -p perry-runtime clean; no new clippy warnings in the touched files

Screenshots / output

$ perry compile url.ts -o url && ./url     # node url.ts
0 /a/c /c                                  # 0 /a/c /c

Related URL test corpus (test-files/*url*.ts plus four adjacent cases) shows no new failures: the only two non-passing entries pre-date this change (test_gap_11519_net_url_short_strings.ts cannot compile locally without libperry_ext_net.a, and test_gap_6375_legacy_url_parse_format.ts differs only on domainToASCII/domainToUnicode lines).

Checklist

• I have NOT bumped the workspace version or edited CLAUDE.md / CHANGELOG.md (maintainer handles these at merge)
• My commits follow the loose feat: / fix: / docs: / chore: prefix convention used in the log
• I've read CONTRIBUTING.md and agree to the Code of Conduct

[coderabbitai]

Caution

Review failed

The pull request is closed.

Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}