Can the README suggest using it? The workaround mentioned in the readme with require('punycode/') does not work with ESM (ERR_UNSUPPORTED_DIR_IMPORT), so there is no way currently to un-ambiguously import punycode in node ESM. I suggest to npm deprecate the punycode module in turn.
The only difference seems to be that 2.1.1 was not published on the punycode.js name.
Publication of both punycode and punycode.js is now automated for every Git tag pushed to this repository! I'm open to a PR that changes the README to recommend the use of punycode.js.
https://www.npmjs.com/package/punycode.js appears to be a complete copy of https://www.npmjs.com/package/punycode, with the benefit that the name is not ambiguous with the deprecated node core module.
Can the README suggest using it? The workaround mentioned in the readme with
require('punycode/')
does not work with ESM (ERR_UNSUPPORTED_DIR_IMPORT), so there is no way currently to un-ambiguously importpunycode
in node ESM. I suggest tonpm deprecate
thepunycode
module in turn.The only difference seems to be that 2.1.1 was not published on the
punycode.js
name.