search

xieziyu / ngx-echarts

An angular (ver >= 2.x) directive for ECharts (ver >= 3.x)
https://xieziyu.github.io/ngx-echarts/
MIT License
1.11k stars 197 forks source link

wrong version is being installed as @latest #126

Closed smnbbrv closed 6 years ago

smnbbrv commented 6 years ago

Hi @xieziyu

When I run npm i ngx-echarts I get the @2.3.1 installed, which is not the expected behavior.

I have angular 6 and latest echarts, so the thing is in the order of publishing (I guess).

See what is latest:

~ npm info ngx-echarts

ngx-echarts@2.3.1 | Proprietary | deps: none | versions: 19
Angular directive for ECharts 3
https://github.com/xieziyu/ngx-echarts#readme

keywords: angular, 2, 4, 5, echarts, ng, ngx, ng2

dist
.tarball: https://registry.npmjs.org/ngx-echarts/-/ngx-echarts-2.3.1.tgz
.shasum: 0c30ca5f2aed28464c1b84d50237f4daf6d2bc15
.integrity: sha512-0aCnTOPN0hA/cTwhNvV113LvHZ3z17g6oUdVrQndZBy0xXX/WFt21eMnyjeMSi3tG+US4DvPyzBq3Ih1ew1waw==
.unpackedSize: 165.9 kB

maintainers:
- xieziyu <xieziyu@foxmail.com>

dist-tags:
latest: 2.3.1

published a week ago by xieziyu <ziyu.xie@foxmail.com>

Still when I run the specific version it is being installed / info is available.

~ npm info ngx-echarts@3.2.0

ngx-echarts@3.2.0 | Proprietary | deps: 1 | versions: 19
 [![Build Status](https://travis-ci.org/xieziyu/ngx-echarts.ssvg)](https://npmjs.org/ngx-echarts)
https://github.com/xieziyu/ngx-echarts#readme

keywords: angular, 2, 4, 5, echarts, ng, ngx, ng2

dist
.tarball: https://registry.npmjs.org/ngx-echarts/-/ngx-echarts-3.2.0.tgz
.shasum: 69bc37d9fc26156117c2c0bb9ba113822228dc43
.integrity: sha512-L1lxf2XuvRn+QPNgbA+wiJBUMIHPUbKMV4PzwNKlEATCqWDWlg1XteJzrrvyxDtbB4OFgv9iVnJtMFFoI0c1FQ==
.unpackedSize: 220.2 kB

dependencies:
tslib: ^1.9.0

maintainers:
- xieziyu <xieziyu@foxmail.com>

dist-tags:
latest: 2.3.1

published a week ago by xieziyu <ziyu.xie@foxmail.com>

That's not too much critical but it is also not that expected and less experienced people might have problems with this. Also I guess the next v3 (or v4) publish automatically fixes the problem, however the tag parameter might be helpful when you are publishing a legacy version: https://docs.npmjs.com/cli/publish

ciukstar commented 6 years ago

Also not critical: On npm outdated

Package           Current  Wanted  Latest  Location
ngx-echarts         3.2.0   3.2.0   2.3.1  arm-analytics-spb
xieziyu commented 6 years ago

@smnbbrv Thank you. I missed that tag.

smnbbrv commented 6 years ago

closing as long as 4* is main for now