How can I determine where the transition dependence of NPM comes from?

I am trying to npm installpackage npm install, but cannot install it due to the lack of a transitive dependency.

(I don’t think the details are important, but we are using the Nexus NPM proxy server, which at that time did not support modules with a scope . One of our dependencies is an attempt to remove the @bahmutov/parse-github-repo-urlmodule, and we get 404.)

In my npm-debug.logI see 404 from our registry:

404 - Path /@bahmutov/parse-github-repo-url not found in group repository</title>

But I can’t say what kind of addiction is trying to deal with it.

Usually I run npm ls [package-name]but this does not work for a project with an empty folder node_modules, which is what happens here.

We use npm3, which has a flat dependency tree, so I can’t just open the partially hydrated folder node_modulesand see where everything is node_modules.

Is there a way to check the file package.jsonand determine the computed dependency tree without relying on npm installfor success?

+9
source share
1 answer

npm-remote-ls looks like it can give you a reasonable answer!

+3
source

All Articles