-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] Depends on deprecated packages path-is-absolute and read-package-tree #4905
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 8.x
work is associated with a specific npm 8 release
Comments
jsha
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 8.x
work is associated with a specific npm 8 release
labels
May 16, 2022
What does Either way, a package being deprecates is not automatically a problem, and isn't necessarily actionable. A package that's not strictly necessary isn't harmful. |
npm explain path-is-absolute
Shorter, with a grep:
|
Sounds like it's a direct dev dep, and also from glob, so your glob PR (once released) would solve most of it, and there's at least one usage directly inside the cli as well that'd need to be removed. |
This was referenced Oct 22, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 8.x
work is associated with a specific npm 8 release
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Hiya! 👋🏻
When I installed the latest npm, I was surprised to see
path-is-absolute
among the dependencies. Its npm page says:On further digging, I found that
read-package-tree
is also deprecated:Here's a quick-and-dirty command I ran to try and figure out where these dependencies came from:
I've filed one PR on node-glob and updated one issue on licensee, but I figured I should open an overall issue on npm/cli for the main issue I'm trying to address.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
The text was updated successfully, but these errors were encountered: