-
-
Notifications
You must be signed in to change notification settings - Fork 260
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
fixes punycode warning #10678
fixes punycode warning #10678
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The native fetch
API is implemented and marked experimental in NodeJS, so soon this can change again to avoid even the import and use native functionality.
…doo into fix-punycode-warning-2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wanna pay your attention on know-good compiler. It still has this warning. Is it a good idea to create an issue for it?
run /var/www/html/qooxdoo/known-good/node_modules/.bin/qx compile --target=build
(node:39891) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
No, that problem should go away after this is released, known-good will automatically become a version with this fix in it. (I think it's automatic anyway! If not we'll just have to update a target version, but can't do that until after this is released) |
The punycode warning is caused by old octokit and node-fetch; both are upgraded
Also this fixes #10669