-
Couldn't load subscription status.
- Fork 53
Closed
Description
Basically just a rehash of npm/cli#2160, npm is expecting pacote to add to cache & pacote has stopped adding to the cache since the big v10 rewrite
What / Why
Pacote fetcher does not add to the cache anymore! npm is expecting this. is npm wrong? Or is pacote wrong?
When
$ npm cache add yn-3.1.1.tgz --cache=./npm-cache
$ ls npm-cache
ls: cannot access 'npm-cache': No such file or directory
Where
Locally, on my machine (no registry, just tarballs)
I appreciate you taking a look at this, if the answer is just that the npm cache command should add to the cache (which does make sense), then great, would just like to verify that that is not under the purview of pacote
Metadata
Metadata
Assignees
Labels
No labels