`tns migrate` clears the platforms and next build fails if a custom android runtime was used

If tns migrate was ran on an app with a custom android runtime (tns platform add android --frameworkPath /test/runtime.tgz), next build would fail. This is because the platforms/android folder is deleted and the version of the tns-android package was previously set in the package.json to the literal next version of the runtime. This runtime, of course, couldn't be found in npm and thus the build fails. Couldn't runtimes added with --frameworkPath be handled differently and in some way marked as such in the package.json? Also, couldn't a simple gradlew clean do the dirty work instead of deleting the whole platforms folder?

Inizia tracciando il punto di ingresso di tns migrate e la gestione di --frameworkPath, quindi esamina come package.json registra la versione di tns-android e come viene rimosso platforms/android. Confronta questo comportamento con l’opzione gradlew clean menzionata. Il lavoro è completato quando la migrazione di un’app con un runtime personalizzato conserva un riferimento al runtime utilizzabile e la build successiva va a buon fine.