Description:
1.Update your CLI to a new version.
2.Run command "ti -v"
Actual Result:
1. You will see that you will still see the old version of the CLI.
2. Trying updating multiple does not help.
3. "sudo npm uninstall", "sudo npm cache clean" & install of CLI also does not work.
4. You have to get rid of
"/usr/local/lib/node_modules/titanium"
& from here
"/usr/local/bin"
as a workaround & possible from this location too
"/Users/--username--/.npm/titanium"
.
Expected Result:
1. We should see the new updated version after updating.
What version of Node.js? What version of npm? What command did you run to install the module? Did you use titanium@
Node Version : v0.10.13 NPM Version : 1.3.2 Yes ran the command : sudo npm install -g titanium@
This may be related to our QE workflow. Meaning things seem to be ok with npm until you need to step back a version (for regression verification) and then try to move forward again. Since a later version appears in the cache, this might be part of the cause. In some cases, our normal "1) uninstall 2) npm cache clean 3) reinstall" did not work and required hand-removing all components and nuking the .npm folder.
I've been testing this over the past few months and have yet to see this issue since. I suspect it was a bug in an older version of npm. I usually keep my npm version to a current version.
Closing ticket as the issue cannot be reproduced.