`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?

Commencez par suivre le point d’entrée de tns migrate et son traitement de --frameworkPath, puis examinez comment package.json enregistre la version de tns-android et comment platforms/android est supprimé. Comparez ce comportement avec l’option gradlew clean mentionnée. Le travail est terminé lorsqu’une migration d’application avec un runtime personnalisé conserve une référence de runtime utilisable et que le build suivant réussit.