parse-domain - npm Package Versions

8.2.2 (2024-08-10)

Bug Fixes

• Lower Expected Min Length (#170) (0f62b8e)

8.2.1 (2024-07-26)

Bug Fixes

• CI deployment (5f7be9a)

Features

• Update PSL (4cbf24d)

8.0.2 (2024-03-04)

Bug Fixes

• Add ParseResultIp to main.js exports (#157) (b5b0177)

8.0.1 (2023-10-27)

Bug Fixes

• Inline sourceContents in source maps (#156) (2f5a249), closes #149

8.0.0 (2023-10-27)

chore

• Update node version (#154) (3a8b92b)

BREAKING CHANGES

• Dropped official support for Node 12, 14 and 16. There wasn't any actual breaking change we know of but use at your own risk :)

7.0.1 (2022-06-30)

Bug Fixes

• Parse error with : when using fromUrl() (09071e6), closes #140

7.0.0 (2022-01-23)

Bug Fixes

• Add support for invalid ipv6 URLs (b32d16c), closes #114
• Remove auto-trimming of input (4ea86a1)

BREAKING CHANGES

• parseDomain won't .trim() the given input. The input is interpreted as it is. If you want to trim the input, you need to call .trim() before passing it to parseDomain. Auto-trimming the input changes the domain and might not be desired if any character (such as whitespace) is allowed (e.g. when using lax validation).

6.0.1 (2022-01-23)

Bug Fixes

• Wrong package exports 🤦‍♀️ (45c5e0c)

6.0.0 (2022-01-23)

• Migrate package to ECMAScript modules (42f54e8)

BREAKING CHANGES

• parse-domain will now be released as native ECMAScript module. There's no CommonJS build anymore. If you're still using CommonJS, you need to import it asynchronously using await import("parse-domain"). If you're still using Node 12, you may need to update it to the latest 12.x version.

5.0.0 (2022-01-23)

Bug Fixes

• Type errors with is-ip module (8ea728c)

Features

• Improve validation (171a8c8)

BREAKING CHANGES

• Introduces a dependency on the global TextEncoder constructor which should be available in all modern engines (see https://developer.mozilla.org/en-US/docs/Web/API/TextEncoder). The strict validation mode (which is the default) will also be a little bit more strict since it will now also check for hyphens at the beginning or end of a domain label. It also requires top-level domain names not to be all-numeric.