Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

peerInvalid: Better error message from npm ls #3080

isaacs opened this Issue Jan 19, 2013 · 6 comments


None yet
5 participants

isaacs commented Jan 19, 2013

It'd be good to have a more useful error message from npm ls in a peerInvalid situation. It should show which package is depending on the invalid one, which package peerDepends on it, etc.

This may require gathering more information in the "problems" list that read-installed collects.

See: #3079 #3047


domenic commented Jan 30, 2013

The code from fc13f37 would probably be ideal for this. Maybe I should pull it out into a separate package.


isaacs commented Jan 30, 2013

Or just work it into readInstalled, maybe? Aren't you just calling readinstalled and doing some stuff to the data object?


domenic commented Jan 30, 2013

Yeah, I guess I am.


smikes commented Feb 9, 2015

/cc @iarna as possibly obsoleted by multi-stage-install

No repro set is provided; no test exists.


othiym23 commented Oct 30, 2015

@smikes I think it would still be useful to have more contextual information about what's going on with peerDependencies when they're unsatisfied, even if peerDependency issues are only a warning. Added onto the road map via the error-handling label.


npm-robot commented Jun 19, 2017

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Jun 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment