Open ghost opened 6 years ago
Really sorry, didn't realise that running npm publish
was failing for me - published now!
(Though the npm seems to be caching the old version for now, just npm install @2.1.9
)
that's ok, thank you.
This is still an issue - NPM still thinks that 2.1.8 is the latest version as of 1/1/2019. In looking at the version history, it looks like 2.1.9 was published and then 2.1.8 was re-published. Was this intentional? Should we not be using 2.1.9?
Absolutely - not sure what the issue is here - just re-published a version 2.1.10 in case I've messed up anything with previous republishes - as I write npmjs.com still shows 2.1.8 as latest but running npm dist-tag ls
prints 2.1.10
as latest - any suggestions? I may very well be missing something
npm doesn't have the last updates