apk-parser | APK parser lib , for decoding binary XML files | Parser library

I wanted to install node-apk-parser:https://www.npmjs.com/package/node-apk-parser into my node js project.It works locally if I run npm install on my VS package manager console. But when I update the package.json on Plesk and hit the button Npm Install and I run my website domain it says "Module not found error for node apk parser"?Node apk parser is at the last. This is my package.json file.

I want to be able to parse APK files from various sources, or various kinds. I want to get only very specific, basic information about them:

• package-name
• version-code
• version-name
• label (app name)
• icon
• minSdkVersion
• whether it's a split APK or not (available when parsing the manifest)

The Android framework has a single function to parse APK files (PackageManager.getPackageArchiveInfo), but it has 2 disadvantages:

1. It requires a file-path. This isn't always available, as you might have a Uri to deal with, or you have the APK file being inside some ZIP file.

2. It can't handle split APK files. Only the base one of them. If you try it on split APK files, you just get null.

Because of this, I've tried to find a reliable, Java&Kotlin solution that can handle them easily.

Each solution I've found has its own disadvatanges. Some libraries I couldn't even find how to use, and some don't have any way to parse APK files without having a real file path. Some of them just create new files instead of returning you objects in Java/Kotlin. Some are even in other programming languages, making me wonder if it's possible to use them.

So far, the only one that I've found as good enough, is "hsiafan" apk-parser, which needs only 2 files within the APK: manifest and resources files. It has some issues, but usually it can get you the information I've mentioned.

Thing is, as I wrote, it's not always working, so I want to return to the basics, at least when I notice it fails to parse, at least for the case that it's a normal APK of base of split-APK files. Some cases it couldn't handle well are:

1. Sometimes the app name couldn't be fetched correctly (here).
2. Some resources are somehow hidden in some apps (here). Even tools such as Jadx fail to show them, but others can.
3. Adaptive icon is hard to parse, including drawable XML files. I succeed parsing VectorDrawable though (here), but it's quite a workaround.

And a few others.

So, I wanted to try out the Android framework again, but this time with a new idea: instead of handling the entire original APK, I could extract only what it really needs, based on the current observation of it.

For example, if I know the resources I need to handle, I can copy only them (and some key files that are needed) into a new APK, and ditch the rest. This could reduce the need to copy/download huge amount of data just to parse the APK and get information about it. If the APK file is 100MB, for example, there is no need to get it all when all we need is just a tiny portion of it.

As a start, I wanted to see how I can create a new APK that can be parsed, so for now I copied all of the entries of the original APK (currently of the current app) into a new file, and chose to parse it: