NPM tns-android Cache being corrupted

[NathanaelA]

This is more an informational post; since I don't have a way to duplicate it yet.

I ran into a case where TNS 2.5 was throwing an warning while installing the tns-android #2475

The issue was caused by somehow a early 2.5.0 @ next ended up in my npm-cache as "2.5.0" so then when tns installing 2.5.0 as normal it was bringing in the early @next version.

[rosen-vladimirov]

Hey @NathanaelA , I've read the other thread and I have an idea how this might have happened. Are you using --frameworkPath parameter? In case you've modified any tns-android package and in its package.json the version has been 2.5.0 (after 2.5.0 release or before it), npm has the disturbing behavior to adds your local package to the npm cache. For example with clean cache:

$ npm i tns-android // installs npm 2.5.0
$ npm install <local path to modified 2.5.0 version of tns-android> - will add my local copy to the npm cache
$ npm install tns-android // gets the version from cache... which is the modified version

Do you think this might be the reason for your issue?

[rosen-vladimirov]

Hey @NathanaelA , as this issue seems caused by npm's work with cache, I'm closing it. Ping me in case you reproduce it and we'll reopen it.