Application Footprint is Huge

[MadMartian]

I find this tool very useful for visualizations and quick adjustments, however the size of the application is absolutely massive at nearly one quarter of a gigabyte. For such a relatively simple application this seems excessive by two orders of magnitude. How can this be improved?

[willrandship]

About 142MB is the main binary+icudtl.dat, which is a sandboxed chrome instance. If it was built to run as a node server that used the user's browser instead of this sandboxed instance, or a system-installed electron installation, it would be much smaller.
Another 105MB is the node_modules folder. Trim out some of the 180 libraries and it becomes a lot smaller, but that would be a relatively involved process.
The other 30MB or so is mostly binary libraries. I'm not sure how much of that is for the browser vs the node server.

If you weren't actively trimming out node libs, you're looking at maybe 150MB available to 'save' by reusing an existing browser/electron, but if this is a minimal install without either of those, it would be a major task to port the application to a different windowing toolkit.