Viewed times. Is there a command that will tell me the current stable version? Improve this question. Community Bot 1 1 1 silver badge. Add a comment. Active Oldest Votes. Improve this answer. Yevgeniy Afanasyev Yevgeniy Afanasyev To install the latest stable, isn't it just npm install bootstrap?
No, it will give you latest, but not stable. For example knockout it gives you "3. Sign up or log in Sign up using Google. Sign up using Facebook. Second: ng decides to download latest stable version from npm to the temporary folder and run it instead of using global version. As the result it takes much longer time to run this command. So it downloads same version twice instead of using global version.
The text was updated successfully, but these errors were encountered:. Hi myemuk ,. This is currently working as intended. However, I do agree we should do better by maybe reusing the temporary version. However this will be part of a bigger overhaul of the ng update experience and also reducing the footprint of the global Angular CLI installation.
It is not used for anything else other than ng new. It's important that ng update always downloads and uses the latest stable version to take advantage of bug fixes and features which effect the update experience. Sorry, something went wrong. Definitely needs to cache this somewhere.
It's super painful doing this from home, over VPN, through the company's firewall. Takes forever :. This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy. If you installed npm with the node. The Node installer installs, directly into the npm folder, a special piece of Windows-specific configuration that tells npm where to install global packages. When npm is used to install itself, it is supposed to copy this special builtin configuration into the new install. There was a bug in some versions of npm that kept this from working, so you may need to go in and fix that up by hand.
Run the following command to see where npm will install global packages to verify it is correct. Incidentally, if you would prefer that packages not be installed to your roaming profile because you have a quota on your shared network, or it makes logging in or out from a domain sluggish , you can put it in your local app data instead:.
Everyone who works on npm knows that this process is complicated and fraught, and we're working on making it simpler. Stay tuned.
0コメント