What I Wanted to Do
Find the official “Last Published” date when the official version of a package was last released, to determine if the package is recent enough to include merged bug fixes.
What Happened Instead
The displayed “Last Published” date on npmjs.com is that of the most recent npm package pushed, not the officially released version.
Visit: Ionic-Angular NPM page (https://www.npmjs.com/package/ionic-angular)
Observe: Official Version (i.e. as of this report, 3.9.4)
Observe: Last Published date (i.e. “5 days ago”)
Visit: Version History page (https://www.npmjs.com/package/ionic-angular)
Observe: Version History -> 3.9.4 without any nightly code (i.e. “2 months ago”)
The official version of Ionic-Angular as of the time this report was filed was 3.9.4. The displayed “Last Published” date states “5 days ago”, the ACTUAL publish date from the version history page shows “2 months ago”.
This left me in a rather confused state when numerous bug fixes merged in the last several weeks were not in the 3.9.4 build. Took time and a bit of digging to ultimately find the ACTUAL publish date on the version history page was two months prior to what I thought it was based on the main NPM page for the package.
I believe the Last Published timestamp should pull from an exact match of package versions, rather than simply the timestamp of the most recent publish. NPM packages can be published under various tags, such as
nightly, and if the OFFICIAL (as in, shown on the npm page) version of a package (i.e. latest) is older than the nightly, that can be misleading and confusing.
Bug is related to npmjs.com, not the CLI. Version information from CLI is not particularly relevant to the issue being filed.