Replace parseurl with WHATWG URL API

[Saturate]

More information here:

e18e/ecosystem-issues#160

[github-actions]

Stale pull request message

[Copilot]

Pull Request Overview

This PR replaces the use of the deprecated parseurl package with the WHATWG URL API to obtain the pathname from the request object.

• Removed dependency on parseurl
• Updated logic for retrieving the request pathname using the WHATWG URL API

Files not reviewed (1)

• package.json: Language not supported

[Copilot]

Using 'new URL(this)' may throw an error if 'this' does not contain an absolute URL. Consider providing a valid absolute URL string or a base URL as the second parameter to ensure proper parsing.

Suggested change

	return new URL(this).pathname;
	const baseUrl = `${this.protocol || 'http'}://${this.host || 'localhost'}`;
	return new URL(this.url, baseUrl).pathname;

[github-actions]

Stale pull request message

[Saturate]

Stale pull request message

Hmm, ok? :)

[github-actions]

Stale pull request message

[Saturate]

Do you need something from me to make this PR easier to close?

[eugef]

Hi @Saturate

Copilot actually caught a real issue here.

• this isn’t a URL, it’s a request object, so you should use new URL(this.url).

• Also, this.url might not always be an absolute URL. parseurl handled relative ones fine, but the URL constructor doesn’t. Adding a base URL (like Copilot suggested) will make sure relative URLs work correctly and avoid potential problems.

Example:

const req = {
    url: '/some/path?name=foo',
}

console.log(parse(req).pathname); // Output: '/some/path'
console.log(new URL(req.url).pathname); // TypeError: Invalid URL