url: skip resolve for already-absolute POSIX paths

[anonrig]

pathToFileURL always called path.resolve, even when the input was already an absolute POSIX path with no . / .. or empty // segments. Reuse that path. Windows UNC and relative paths still go through path.resolve.

Official benchmark/url/whatwg-url-to-and-from-path.js (--no-node-snapshot, 4 alternating runs vs parent):

method	input	change
pathToFileURL	/dev/null	+27%
pathToFileURL	/dev/null?key=param&bool	+48%
pathToFileURL	/dev/null?key=param&bool#hash	+45%
pathToFileURL	file:///dev/null (relative path string)	~0%
fileURLToPath	file:///dev/null	~0%

test/parallel/test-url-pathtofileurl.js and test-url-fileurltopath.js pass. A closed-source coding agent assisted with the implementation.

  

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 4520770. Configure here.}

[cursor]

Trailing slashes doubled on Windows

Medium Severity

Skipping path.resolve keeps a trailing slash on already-absolute POSIX paths. The later restore still appends another slash when resolved does not end with path.sep. On Windows, path.sep is a backslash, so pathToFileURL with windows: false emits a double slash and a wrong file: URL for directory paths.

Additional Locations (1)

• lib/internal/url.js#L1713-L1720

 

^{Reviewed by Cursor Bugbot for commit 4520770. Configure here.}