How do you compact dependencies into an asar if there are so many dependencies?

[matthew-dean]

So, I'm somewhat confused how this might be managed in terms of turning node_modules into an asar archive.

That is: I've generated an asar archive. Great. BUT asar-fs lists asar as a dependency, and asar itself has a significant list of dependencies. So... do you get what I'm getting at? How can I use asar-fs with node_modules, if my node_modules are in an .asar file? I know that I can exclude the /asar-fs module from the ASAR file, but what about its dependencies, and its dependencies dependencies etc? What's the correct approach here?

[CKarper]

This project was a poc spin off from the nexe project, which bundles your node scripts into a custom node build.

Without something else to bootstrap the process, you're right that you can't get rid of all the dependencies.