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
DeprecationWarning: Punycode #17720
Comments
Hi @jasperkelder, thanks for the issue. I don't think this is something to be solved in ESLint. ESLint directly depends on |
I've opened a PR to fix this in uri-js, the package ajv depends on here: garycourt/uri-js#95 |
@domdomegg |
@newinfinity12 perhaps this #13888 (comment) will help you understand why ESLint still uses |
@Rec0iL99 Based on the threads created in Ajv and URI.js the blame/fix keeps getting pushed around to different repos. Ajv has not been updated in over a year and URI.js in over 3 years. So based on this info it looks like eslint should switch to a different repo to avoid the deprecation warning altogether |
@newinfinity12 the way node resolves dependencies will mean that updating uri-js as a minor or patch version will still fix it, even though eslint uses ajv 6 |
@domdomegg |
@Rec0iL99 eslint will require an update to fix this whenever ajv eventually fixes it, so either way this issue should remain open here (especially given how far behind on major/minor versions eslint is for ajv). Fyi to all: you can also |
Hi there,
https://github.com/andreinwald/uri-js-replace You can add to package.json of your project: "overrides": {
"uri-js": "npm:uri-js-replace"
} |
Did not work for me. |
ESLint version
8.53.0
What problem do you want to solve?
One of eslint's dependencies is using a deprecated module, we're currently getting the following warning -> DeprecationWarning: The
punycode
module is deprecated. Please use a userland alternative instead.└─┬ eslint@8.53.0
└─┬ ajv@6.12.6
└─┬ uri-js@4.4.1
└── punycode@2.3.0
What do you think is the correct solution?
Make sure the deprecated module gets replaced in the dependency tree.
The text was updated successfully, but these errors were encountered: