-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Legacy URL is not deprecated anymore - node/no-deprecated-api
#339
Comments
Still do not think that ppl should use |
It's fine if developers/teams decide not to use |
We switched to it in eg. Try that module out and if it isn't fixed there, then open a new issue in that project. |
It seems that
url.parse
and others as part of the Legacy URL API are no longer deprecated as of nodev14.17.0
. I don't believe they should triggernode/no-deprecated-api
.This was specifically an issue in our projects given than
url.parse(path)
is not the same asnew URL(path)
when the path is relative. See issues for more:The text was updated successfully, but these errors were encountered: