I published an npm module about a day ago and have bumped the version a couple of times since then. In the beginning, there was 0.0.0, then 0.0.1, now sitting at 0.1.1.
When I visit the https://www.npmjs.com/package/skipper-minio everything looks okay - versions, published date, my stupid face are all there.
The 'issue' I'm seeing though, is that when you do a search that returns said module using either of the web interface at npmjs.com or the npm command line utility the version is still at 0.0.0, the published date is 'Invalid'/'prehistoric' and the description and other meta stuff is unavailable.
Command line search result
$ npm search skipper-minio
NAME | DESCRIPTION | AUTHOR | DATE | VERSION | KEYWORDS
skipper-minio | | | prehistoric | 0.0.0 |
Web search result
Actually installing the module in a 'fresh' project with npm install --save skipper-minio or skipper-minio@latest both do what they should and install the actual latest 0.1.1 version.
So, is this just a matter of caching at the npmjs.com / npms.io side, is my package.json breaking things, or is something more mischievous afoot?
来源：https://stackoverflow.com/questions/55761863/have-i-broken-npm