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

False positive for cached package version #35

Closed
JamieMason opened this issue Apr 19, 2016 · 1 comment
Closed

False positive for cached package version #35

JamieMason opened this issue Apr 19, 2016 · 1 comment

Comments

@JamieMason
Copy link
Owner

shrinkpack tried to read [email protected] from the cache...

! failed to read file /Users/jmason/.npm/object-assign/3.0.0/package.tgz
! failed to shrinkpack [email protected]
! Please raise an issue at https://github.com/JamieMason/shrinkpack/issues

    Error: ENOENT: no such file or directory, open '/Users/jmason/.npm/object-assign/3.0.0/package.tgz'
        at Error (native)

but it was not there, although other versions were.

$ npm cache ls | grep object-assign
~/.npm/object-assign/
~/.npm/object-assign/2.1.1/
~/.npm/object-assign/2.1.1/package.tgz
~/.npm/object-assign/2.1.1/package/
~/.npm/object-assign/2.1.1/package/package.json
~/.npm/object-assign/4.0.1/
~/.npm/object-assign/4.0.1/package.tgz
~/.npm/object-assign/4.0.1/package/
~/.npm/object-assign/4.0.1/package/package.json
@JamieMason JamieMason added the bug label Apr 19, 2016
@JamieMason JamieMason changed the title False positive for cache package version False positive for cached package version Apr 19, 2016
@JamieMason
Copy link
Owner Author

This can happen when the package.json used to resolve the tarball does not match the version required.

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

No branches or pull requests

1 participant