Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] running ls after clean-install for git dependency shows UNMET DEPENDENCY #623

Closed
msbit opened this issue Dec 21, 2019 · 2 comments
Closed
Labels
Bug thing that needs fixing

Comments

@msbit
Copy link

msbit commented Dec 21, 2019

What / Why

Running npm ls after npm clean-install, on a project that has a git dependency (eg https://github.com/lodash/lodash) shows that dependency as being unmet (UNMET DEPENDENCY)

When

Every time npm ls is run after npm clean-install, with a git dependency

Where

  • npm/cli ?

How

Current Behavior

[email protected] /Volumes/Suffragette/Development/msbit/npm-clean-install-ls-error
└── UNMET DEPENDENCY lodash@git+https://github.com/lodash/lodash.git#cefddab1cab49189b2ff4d72acf8df7ec723dc22

npm ERR! missing: lodash@git+https://github.com/lodash/lodash.git, required by [email protected]

Steps to Reproduce

Run attached script, but effectively:

  • npm install https://github.com/lodash/lodash
  • rm -rf node_modules
  • npm clean-install
  • npm ls

Expected Behavior

[email protected] /Volumes/Suffragette/Development/msbit/npm-clean-install-ls-error
└── [email protected] (git+https://github.com/lodash/lodash.git#cefddab1cab49189b2ff4d72acf8df7ec723dc22)

Who

  • Unsure
@darcyclarke darcyclarke added the Bug thing that needs fixing label Oct 30, 2020
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

@msbit
Copy link
Author

msbit commented Jun 3, 2021

Thanks @darcyclarke. Checking against npm 7.15.1 doesn't show the error, so I'd say it's been sorted out 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing
Projects
None yet
Development

No branches or pull requests

2 participants