Open
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
Hiya! 👋🏻
When I installed the latest npm, I was surprised to see path-is-absolute
among the dependencies. Its npm page says:
This package has been deprecated
This package is no longer relevant as Node.js 0.12 is unmaintained.
On further digging, I found that read-package-tree
is also deprecated:
The functionality that this package provided is now in @npmcli/arborist
Here's a quick-and-dirty command I ran to try and figure out where these dependencies came from:
$ rg path-is-absolute -l | grep package.json
node_modules/path-is-absolute/package.json
node_modules/tap/node_modules/path-is-absolute/package.json
node_modules/tap/node_modules/glob/package.json
node_modules/read-package-tree/node_modules/glob/package.json
node_modules/test-exclude/node_modules/glob/package.json
node_modules/tap-mocha-reporter/node_modules/glob/package.json
node_modules/nyc/node_modules/glob/package.json
node_modules/node-gyp/node_modules/glob/package.json
node_modules/rimraf/node_modules/glob/package.json
workspaces/arborist/test/fixtures/install-types/node_modules/glob/package.json
workspaces/arborist/test/fixtures/install-types/node_modules/path-is-absolute/package.json
workspaces/arborist/test/fixtures/global-style/lib/node_modules/rimraf/node_modules/glob/package.json
workspaces/arborist/test/fixtures/global-style/lib/node_modules/rimraf/node_modules/path-is-absolute/package.json
workspaces/arborist/test/fixtures/tap-with-yarn-lock/node_modules/path-is-absolute/package.json
workspaces/arborist/test/fixtures/tap-with-yarn-lock/node_modules/babel-core/package.json
workspaces/arborist/test/fixtures/tap-with-yarn-lock/node_modules/glob/package.json
$ rg read-package-tree -l | grep package.json
node_modules/read-package-tree/package.json
node_modules/licensee/package.json
workspaces/arborist/test/fixtures/root/node_modules/foo/node_modules/express/package.json
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