Running custom builds (or nightlies) breaks with new TNS CLI Master

[NathanaelA]

I upgraded to v1.5 nightly of everything 2015/11/04; but I ran into a issue with it that required me to disable some code inside the tns command line tool.

Here is the problem:
When you do a tns prepare (or anything internally does a tns prepare) it runs a function called NpmInstallationManager.prototype.isShasumOfPackageCorrect
Well, this function attempts to do a npm view tns-android@1.5.0 (or whatever version the built runtime is labeled). Of course since this is a compiled master installed using --frameworkPath; this sha will not be in the npm log. So npm fails to be to get a sha hash. If you label the custom runtime 1.4 (i.e. whatever is current) then of course the sha hash won't match.

I haven't had these problems ever before; so I am "assuming" this code is new in the master branch of the CLI; or their is some other bug that is causing a prepare to force a sha check of the runtimes which will for sure fail.

[teobugslayer]

Hi @NathanaelA, which version of CLI are you using? I cannot reproduce this behavior with CLI from master.

[teobugslayer]

Thanks for the repro case, I'll have a look at the issue