Question about necessity of multiple AAR files in npm package - impacting yarn zero installs

I'm using yarn zero installs and need to store npm packages compressed in the repository. However, the NativeScript Android npm package contains three large AAR files that are causing issues with GitHub's 100MB upload limit:

• framework/app/libs/runtime-libs/nativescript-optimized-with-inspector.aar (~32MB)
• framework/app/libs/runtime-libs/nativescript-optimized.aar (~30MB)
• framework/app/libs/runtime-libs/nativescript-regular.aar (~32MB)

Together with all other files these exceed the 100MB limit, making it impossible to commit the compressed packages to the repository.

Question: Are all three of these AAR files actually necessary? Could some of them be made optional or combined to reduce the package size for users who want to use yarn zero installs?

This would greatly help developers who need to maintain reproducible builds with yarn zero installs but are hitting the repository size limits due to these large runtime files.

Another affected NPM package is @nativescript/types-android.

Start by examining the three AAR files under framework/app/libs/runtime-libs and how they are referenced by the NativeScript Android npm package. Determine whether each runtime variant is required, including for @nativescript/types-android, and define done as reducing package size without breaking supported Android builds or yarn zero-install packaging.