Url Toolkit Versions Save

Scheme regex is now a bit stricter.

It now must match [a-zA-Z0-9+\-.] as described in the RFC.

This means relative urls that happen to contain ‘:’ are more likely to be recognised as relative providing they contain a character that does not satisfy the above.

Also updated the README mentioning that if you know a URL is relative, you should prefix it with ./.

Fix typescript types export

Adds typescript type definitions.

Fix bug in regex.

This should be backwards compatibile with version 1 if the alwaysNormalize option is set to true. This option is required as normalization should only be performed if necessary, according to the spec.

The one exception is a combination like "http://a.com/b/cd?test=1#something" + ";x", which previously incorrectly being resolved as "http://a.com/b/;x", instead of "http://a.com/b/cd;x". To loose the last segment of the path the relative URL should be "./;x".

Handle base url protocol being '//'.

This was not working properly when the relative url started with '/' or '//'.

• Handle no protocol properly.
  • a.com + z.ts => a.com/ + z.ts => a.com/z.ts not a.com + z.ts => z.ts
• Improve performance slightly by reusing expressions.

Handle any unicode string as domain name and allow baseURL to omit protocol and slash(es).

See https://en.wikipedia.org/wiki/Domain_name#Internationalized_domain_names

The character set allowed in the Domain Name System is based on ASCII and does not allow the representation of names and words of many languages in their native scripts or alphabets. ICANN approved the Internationalized domain name (IDNA) system, which maps Unicode strings used in application user interfaces into the valid DNS character set by an encoding called Punycode. For example, københavn.eu is mapped to xn--kbenhavn-54a.eu. Many registries have adopted IDNA.

Handle missing '/' after domain

Fix JSLint error.