docs(@angular/cli): Update 1.0 upgrade guide #5876
Conversation
| ``` | ||
|
|
||
| ### Manually removing residual Angular CLI | ||
|
|
||
| If you accidentally updated NPM before removing the old Angular CLI, you may find that uninstalling the package using `npm uninstall` is proving fruitless. This is because under linux and OSX, NPM changed its global install (and uninstall) path during the upgrade process from `/usr/local/lib` to just `/usr/lib`, and hence, no longer searches through the old directory. In this case you'll have to remove it manually: |
There was a problem hiding this comment.
This is because under linux and OSX, NPM changed its global install (and uninstall) path during the upgrade process from /usr/local/lib to just /usr/lib, and hence, no longer searches through the old directory
This is not a given, it very much depends on how node is installed. If node is installed using brew the installation location stays the same and this is not an issue.
There was a problem hiding this comment.
Ok, I updated with new wording, let me know what you think
Added a few extra details on how to remove residual versions of Angular CLI and reorganized upgrade steps.
Added a few extra details on how to remove residual versions of Angular CLI and reorganized upgrade steps. Fixes angular#5842
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Added a few extra details on how to remove residual versions of Angular CLI and reorganized upgrade steps.
Fixes #5842