Hi Justin, I did some test and found that "npm dist-tag add [email protected] latest" can make 4.1.0 version (our latest approved release version) to be latest, and "npm install echarts" will install this version. The "4.2.0-rc.2" will be only installed with "npm install [email protected]".
Does that work for you? Zhang Wenli http://zhangwenli.com On Wed, Feb 6, 2019 at 2:59 PM Justin Mclean <[email protected]> wrote: > HI, > > > Good news that there is a nuance here about advertised vs. available. > > So the previous email I wrote should work to get you guys into > compliance. > > I'm not so sure, currently they are advertising a RC to the general > public, as far as I understand deprecating a release only gives a user a > warning when they try to install it. I'm not sure it removes it from this > page [1]. The documentation states "This command will update the npm > registry entry for a package, providing a deprecation warning to all who > attempt to install it." [2] I not sure that providing a warning what still > having it publicly available is enough. > > Thanks, > Justin > > 1. https://www.npmjs.com/package/echarts > 2. https://docs.npmjs.com/cli/deprecate > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
