You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
Current Behavior:
When there is a git dependency in the "dependencies" that point to specific hash.
NPM mirrored the complete repo.
Expected Behavior:
NPM only pull specific commit unless there is no server support of fetch by commit.
Since 2015,
It is possible to fetch a commit directly with sha1 hash with following sequence. (if the server enabled that function)
https://stackoverflow.com/questions/14872486/retrieve-specific-commit-from-a-remote-git-repository/30701724#30701724
Steps To Reproduce:
git+https://github.com/xtermjs/xterm.js.git#0320e6e22a67fe5d50b07df1d9f310684df2e561
to package.jsonnpm i
git
process spawned by npm with ps/top/htopEnvironment:
The text was updated successfully, but these errors were encountered: