NPM Publish about pluralize

[benmarch]

Sorry about that, it was indeed cached (I did run npm info just prior to opening the issue). I can see 6.0.0 now.

[benmarch]

@blakeembrey yes I was using my company's registry at the time, and it has a 24h cache period. I'll be sure to bypass it next time I run npm info. BTW I'm now using change-case as well, these are awesome libraries! Thank you!

[blakeembrey]

Try 6.0.0?

[blakeembrey]

Also, it was released two hours before this issue: https://github.com/blakeembrey/pluralize/releases/tag/v6.0.0. From npm info pluralize:

Are you running into some other issue or were you just looking at an outdated page? I don't tag releases on GitHub until after NPM publish usually, so it's odd you'd run into this issue.

[wopian]

The npm package page (sometimes?) gets cached for a few hours - so could well have been displaying 5.0.0 as the latest instead of 5.1.0 at the time (but installing 5.1.0)

[blakeembrey]

Thanks @wopian. I've noticed the NPM web cache issue before, but never with package/info outdated. @benmarch are you perhaps using a different registry? Glad it's working now either way.