The question is advisory in nature. I want to understand why it is so and not otherwise.
So, I go and put typescript:
>npm install typescript --save `-- typescript@2.0.10 The installed version is the stable version of typescript, which is currently 2.0.10.
However, I know that there is an RC with version 2.1.1 . Let's see what npm update does:
>npm update typescript `-- typescript@2.1.1 Yeah, I see. Update has upgraded to RC and now I have typescript version 2.1.1.
Now I want to look at outdated packages, what do I see?
>npm outdated Package Current Wanted Latest Location typescript 2.1.1 2.1.1 2.0.10 folder Here questions arise:
Why is 2.1.1 considered outdated? From the description of npm update it may be possible to think that once the installed version is = = latest, the package is considered outdated, but it still doesn’t say "black in white"
Why does npm update install, in this case, packages that can be RC? And if I write a script, which will periodically update the packages? - then at some point I can get a not too secure system, having new NOT stable packages
Well, it’s generally strange that current can be more than latest. Even if RC is set, I would like to have some notification of this when displaying the list of packages.
