bundlejs VS pako

Package Size Checker

I was closing out some long lived issues over on bundlejs, when issue #50 reminded me of the ongoing debate about how bundlejs should handle the ESM and CJS packages.

Still, I'm not really sure about its dependencies: it lists react and @tanstack/react-query (as opposed to @tanstack/query-core) and bundlejs reports 124KB gzipped. Also, while using it, you still need to refer to their react docs (that documentation is really good and has a lot of examples) but not everyone will be thrilled about checking a react documentation when they're using an angular package.

It's somewhere in between.

React as a lib and architecture _is_ platform-agnostic. The core logic is defined in the `react-reconciler` package. It contains all the implementation of rendering components, diffing trees, managing state, and running effects, as well as all the "Suspense" implementation.

However, the way `react-reconciler` works is that it's built _into_ each platform-specific renderer implementation. So, the size of `react-dom` is actually the size of `react-reconciler` + all the DOM-specific behavior.

A quick check of https://bundlejs.com/?q=react-reconciler suggests it's about 100K minified. https://bundlejs.com/?q=react-dom is 138K, so that tells me that the DOM-specific logic is 38K.

React Hook Form has no dependencies and a small bundle size. It has a gzipped bundle size of 12.12KB, according to bundlejs.

These are shameless plugs, but https://bundlejs.com and https://inthistweet.app. I built both tools specifically because I didn't find any other tools that solved the problems I kept running into.

Try https://bundlejs.com/ to see

bundlejs (pronounced bundle js) is a quick and easy way to treeshake, bundle, minify, and compress (in either gzip or brotli) your typescript, javascript, jsx and npm projects, while receiving the total bundles' file size.

Don't know of any but was going thru Adam Wathan's twits and replies. Found, https://github.com/okikio/bundle Looks medium sized.

try pako

A trick I've used on top of serializing JSON in the URL is in-browser compression with a library like pako [0] (zlib in JavaScript). This helps you get more data in before you reach the browser limit for URL length.

[0] https://github.com/nodeca/pako

Another operation that is sometimes desired is to take several files and give the user a compressed file. There are actually a surprisingly large amount (jszip, pako) of client side options here, but my favorite so far when it comes to speed, size and working with .zip has been fflate. But if you'd like to work with other formats, there are also libraries to decompress 7-Zip, RAR & TAR.

I used monaco-editor for the code-editor, esbuild and rollup as bundler and treeshaker respectively, pako as a js port of the zlib and gzip libraries, pretty-bytes to convert the gzip size to human readable values, and countapi-js to keep track of the number of page visits, in a private and secure way.

Just wanted to let you know the most current version of pako does not work with the example on the wiki page. It errors out with "unknown compression format". I had to use the version found in Toolbox lib folder in order to get the example from the wiki page to work.

Uncompressing should be straightforward with pako.js.