The problem with new URL(), and how URL.parse() fixes that | Kilian Valkhof

As someone building a browser I need to parse a lot of URLs. Partially to validate them, but also to normalize them or get specific parts out of the URL. The URL API in browsers lets you do that, but it’s ergonomics aren’t ideal. The problem with new URL() The “new” in front of new URL() indicates that it’s used as a constructor: calling it creates a new URL instance for you. When you give it a ma

[mukaken]

new URL() の問題と、URL.parse() がその問題を解決する方法

[jay-es]

new URL は引数が不正だとにエラーになる。try-catch で囲むとコードが多くなるし変数宣言が let になる。`URL.canParse(urlstring) && new URL(urlstring)` と書くとシンプル。canParse は新しめのメソッドなので注意