-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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] cache add
tarball file does not add to cache
#2160
Labels
Bug
thing that needs fixing
Priority 2
secondary priority issue
Release 7.x
work is associated with a specific npm 7 release
Comments
mjsir911
added
Bug
thing that needs fixing
Needs Triage
needs review for next steps
Release 7.x
work is associated with a specific npm 7 release
labels
Nov 12, 2020
mjsir911
changed the title
[BUG]
[BUG] Nov 12, 2020
cache add
does not add to cachecache add
tarball file does not add to cache
Does this still happen on npm v7.0.10? |
Can reproduce with npm@7.0.10, node v15.1.0 |
darcyclarke
added
Priority 2
secondary priority issue
and removed
Needs Triage
needs review for next steps
Enhancement
new feature or improvement
labels
Feb 2, 2021
This was referenced Mar 27, 2021
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Mar 27, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Mar 27, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Mar 27, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Mar 27, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Mar 28, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Apr 1, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/cli
that referenced
this issue
Apr 1, 2021
Pacote doesn't do this automatically anymore Closes npm/pacote#73 & Closes npm#2160
mjsir911
added a commit
to mjsir911/pacote
that referenced
this issue
Apr 1, 2021
Tell `fetch` not to cache it's downloaded tarballs, leave that to us Not sure the implications of changing the return type of _istream / adding a `cacache` to the end of the pipe, too unfamiliar with streams Fixes npm#73 & Fixes npm/cli#2160 Also see npm/cli#2976 for my first attempt & some discussions as to how we got here.
isaacs
pushed a commit
to npm/pacote
that referenced
this issue
Apr 13, 2021
Tell `fetch` not to cache it's downloaded tarballs, leave that to us Also see npm/cli#2976 for my first attempt & some discussions as to how we got here. Fix: #73 Fix: npm/cli#2160 Close: npm/cli#2976 PR-URL: #74 Credit: @mjsir911 Close: #74 Reviewed-by: @isaacs EDIT(@isaacs): Updated to add test, allow make-fetch-happen to use the cache, pipe into cache properly, and avoid cache double-writes.
isaacs
pushed a commit
to npm/pacote
that referenced
this issue
Apr 13, 2021
Tell `fetch` not to cache it's downloaded tarballs, leave that to us Also see npm/cli#2976 for my first attempt & some discussions as to how we got here. Fix: #73 Fix: npm/cli#2160 Close: npm/cli#2976 PR-URL: #74 Credit: @mjsir911 Close: #74 Reviewed-by: @isaacs EDIT(@isaacs): Updated to add test, allow make-fetch-happen to use the cache, pipe into cache properly, and avoid cache double-writes.
isaacs
pushed a commit
to npm/pacote
that referenced
this issue
Apr 15, 2021
Tell `fetch` not to cache it's downloaded tarballs, leave that to us Also see npm/cli#2976 for my first attempt & some discussions as to how we got here. Fix: #73 Fix: npm/cli#2160 Close: npm/cli#2976 PR-URL: #74 Credit: @mjsir911 Close: #74 Reviewed-by: @isaacs EDIT(@isaacs): Updated to add test, allow make-fetch-happen to use the cache, pipe into cache properly, and avoid cache double-writes.
isaacs
pushed a commit
to npm/pacote
that referenced
this issue
Apr 15, 2021
Tell `fetch` not to cache it's downloaded tarballs, leave that to us Also see npm/cli#2976 for my first attempt & some discussions as to how we got here. Fix: #73 Fix: npm/cli#2160 Close: npm/cli#2976 PR-URL: #74 Credit: @mjsir911 Close: #74 Reviewed-by: @isaacs EDIT(@isaacs): Updated to add test, allow make-fetch-happen to use the cache, pipe into cache properly, and avoid cache double-writes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug
thing that needs fixing
Priority 2
secondary priority issue
Release 7.x
work is associated with a specific npm 7 release
Current Behavior:
The only index file looks like this:
Which explains why it doesn't show up with
--offline
, but there are nopacote
tarball files cachedExpected Behavior:
npm cache add
should cache the tarball passed to it, resulting in index files that look like this, even in offline mode (this file was created withnpm@6.14.5
:Of note,
npm cache add https://registry.npmjs.org/yn/-/yn-3.1.1.tgz
sort of works properly, resulting in an additional index file containing this:Environment:
The text was updated successfully, but these errors were encountered: