-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
punycode exports nothing if global AMD define
is present
#7224
Comments
Node core grabs punycode as is from https://github.com/bestiejs/punycode.js/. You might want to consider opening an issue there. |
I figured as much but thought it might be a good idea to track the problem on both projects. |
Patch that updates to Punycode.js v2.0.0, which only exports to |
Fishrock123
pushed a commit
that referenced
this issue
Jun 27, 2016
Punycode v2.0.0 drops support for old and non-Node environments. PR-URL: #7267 Fixes: #7224 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
Fishrock123
pushed a commit
that referenced
this issue
Jul 5, 2016
Punycode v2.0.0 drops support for old and non-Node environments. PR-URL: #7267 Fixes: #7224 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Roman Reiss <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an AMD loader is defined on
global
, the punycode module no longer exports something if required with Node'srequire()
:In particular, this affects
Url.prototype.parse()
method, which has a dependency onpunycode.toASCIII()
.The text was updated successfully, but these errors were encountered: