Not sure why I try to upgrade so many big libraries to TS and ESM, it gets complicated quickly hehe.

My goal is that I want to have something like JSZip, but build using only vanilla library features, and to be fully ESM compatible, as well as have first-party type definitions. Also, using a Promise-based API is key as well.

https://stackoverflow.com/questions/14527820/does-html-5s-blobbuilder-still-work-in-google-chrome
https://gist.github.com/eligrey/1079572/aeac96e31f03bb8aeecedd5e5a6a89ac92c106cc
https://www.google.com/search?q=require%28%27setimmediate%27%29
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/concat
https://stackoverflow.com/questions/29676635/convert-uint8array-to-array-in-javascript

Going to go from the bottom of the module tree to the top, to make the whole codebase type-safe! This is going to take a few different sessions.

I'm considering whether I should do this with a fork of the library instead, and work on modernizing that instead of the original, which seems to be a few development iteration types back (ESM, TypeScript, browser-first).

https://github.com/telerik/jszip-esm

It seems like a lot of work for modernizing older projects like these are that they are for Node to start with, and there are a lot of polyfills set up to make it work for modern code, rather than the other way around. To be fair, that's the same issue I'm having with my own projects from a few years ago too, so it's just going to happen, and it's still just something we have to deal with. I guess it's good that the same language has been around long enough for it to grow so much to where that is a concern. People see that as a downside to the JS ecosystem, but it also really shows how much things have grown over the years.

I wish not as many new TS projects were OOP, it's still the same language under the hood, so I find it interesting how the typings for things in that manner seems to have brought non-FP concepts over to JS's fairly functional neighborhood (at least for packages, it seems like most user-facing APIs use functions where possible, and maybe the underlying implementation may use a few classes).