npm.io
6.2.2 • Published 4d agoCLI

idna-uts46-hx

Licence
MIT
Version
6.2.2
Deps
1
Size
678 kB
Vulns
0
Weekly
0
Stars
14

IDNA-UTS #46 in JavaScript

npm version node semantic-release License: MIT PRs welcome

This module is a IDNA UTS46 connector library for javascript. In addition to the default functionality of tr46, we offer converting domain names to unicode / punycode considering the respective registry provider's behavior.

The JS Punycode converter library is a great tool for handling Unicode domain names, but it only implements the Punycode encoding of domain labels, not the full IDNA algorithm. In simple cases, a mere conversion to lowercase text before input would seem sufficient, but the real mapping for strings is far more complex. This library implements the full mapping for these strings, as defined by UTS #46.

Resources

Command Line Interface

The package ships the idna-uts46-hx executable. Use it without installing:

npx idna-uts46-hx öbb.at
# öbb.at	xn--bb-eka.at

By default every input domain name is printed as <unicode> and <punycode>, separated by a tab. Restrict the output to one of both representations with --to:

idna-uts46-hx --to ascii faß.de
# xn--fa-hia.de

idna-uts46-hx --to unicode xn----5da7e.de
# ä-ü.de

Domain names can be passed as arguments or piped in via stdin, one per line, which makes bulk conversion straightforward:

cat domains.txt | idna-uts46-hx --to ascii > punycode.txt

Use --json for machine-readable output, including per-domain error messages:

idna-uts46-hx --json öbb.at
# [
#   {
#     "input": "öbb.at",
#     "IDN": "öbb.at",
#     "PC": "xn--bb-eka.at"
#   }
# ]
Options
Option Description
-t, --to <mode> ascii, unicode or both (default: both)
-j, --json emit JSON instead of plain text
-s, --separator column separator for mode both (default: tab)
--transitional force transitionalProcessing on
--no-transitional force transitionalProcessing off
--std3 apply useSTD3ASCIIRules
--verify-dns-length apply verifyDNSLength
--check-hyphens apply checkHyphens
--check-bidi apply checkBidi
--check-joiners apply checkJoiners
-h, --help show the help
-v, --version show the version

Without --transitional / --no-transitional, transitional processing is auto-detected from the TLD, just like in the library API.

The exit code is 0 when all conversions succeeded, 1 when at least one domain name could not be converted (the reason is written to stderr, the remaining domain names are still processed) and 2 on invalid usage.

v6 Notes & Migration Guide

With v6 we migrated our library to npm package tr46 as software dependency. By that step we use a library that is actively maintained in direction of correctly supporting the TR46 standard and supporting the latest Version of the Unicode Standard. Reinventing the wheel isn't useful and something we have time or resources for. We were able to dramatically decrease the number of lines of code on our end.

Improvements
  • method toUnicode comes with auto-detection of transitionalProcessing setting based on the provided domain name input
  • method toAscii comes with auto-detection of transitionalProcessing setting based on the provided domain name input
Breaking Changes

In general, we don't see a blocker for upgrading to v6. Still, consider the below changes.

Performance

Runtime performance of v6 compared to v5 has slightly improved. The compression for the underlying idna mapping table is superfluous, tr46 covers it well.

New Labels for Options

The below configuration options for the methods toUnicodeand toAscii must be renamed in case you're using them:

Option, old Option, new
transitional transitionalProcessing
useStd3ASCII useSTD3ASCIIRules
verifyDnsLength verifyDNSLength
Behavior

Earlier versions kept option transitional by default to false which is now automatically detected and results may therefore differ. This affects the toAscii method.

The toUnicode function did not allow for a options parameter in earlier versions, now it follows the exemplary way of package tr46.

Authors

Thanks for the below former contributions:

  • Initial work done by jcranmer.
  • v5: Migration of the IDNA Mapping Table's Build Process from Python to NodeJS5 by dawsbot
  • v5: Performance Improvements for the Browser Bundle's Page Load by dawsbot

See also the list of contributors who participated in this project.

License

MIT

Keywords