I'm in favor of this.
@DesignByOnyx the tests are failing because lack of coverage for the Unrecognized URL error path.

I think I would also prefer if the invalid protocol TypeError was thrown from inside of normalizeUrl instead of the Scope constructor.

@mastermatt - I have made the updates you requested. Thanks for the quick review.

A quick note on the change I made:

I got rid of the Unrecognized URL error. Instead, users can pass a legacy url object (url.parse(...)) or anything that the URL constructor supports (strings and URL instances as of this writing). If a user passes an invalid URL, I am letting the URL parser report the error.

Apologies, I had some trailing whitespace in there. I thought I had run the formatter. Should be good to go.

🎉 This PR is included in version 13.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀