I really have no idea how that is achieved, the cordava CLI converts the JS code into a APK, but surely the Java code must be there around, actually I think it is inside the the folder platform/android
We did that before. You can search cordova and you can found many examples. IIRC we required some upstream authors to provide that in a f-droid specific tag. It’s still source code but generated from js.
Just run cordova platform add android. Then we can run gradle assembleRelease in platforms/android/app. NodeJS is not really a problem since we use it for many ReactNative apps. But for cordova apps we can avoid that so that we don’t need to
install node. node in debian is old and we usually need to download it from upstream.
install cordova and run cordova platform add android
find the output apk manully.
Basically the cordova build --release android is the same as gradle assembleRelease. Our build system works better with gradle and it can make the recipe simple.
This is a valid point @linsui , the generated JAVA code obtained from cordova build --release android is far from human readable and thus amendable/workable by humans. Furthermore many developers, such as myself, use a hook to previously minify the JS code upon build, which makes the JAVA code even more human unreadable