Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm.commands.ls does not includes new installs #2930

Closed
Gozala opened this issue Nov 6, 2012 · 2 comments
Closed

npm.commands.ls does not includes new installs #2930

Gozala opened this issue Nov 6, 2012 · 2 comments

Comments

@Gozala
Copy link
Contributor

Gozala commented Nov 6, 2012

It looks like ls does some caching that prevents it to from returning new results. Here is reproducible test case:

https://gist.github.com/4021511

@mfncooper
Copy link
Contributor

Yep, this is a bug, actually in the read-installed package. There are a few module-level vars that are used to stash data as the result is built up, and they're not being reset for each call to readInstalled().

@npm-robot
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants