Christopher Dieringer

I discovered that any consumption of the `Js` module is that which adds approx 50kb+ of javascript ```sh $ ocamlfind ocamlc -package js_of_ocaml -package js_of_ocaml-ppx -linkpkg js/main.ml -o js/main.bc $...

What i'm after is specifically: https://github.com/webpack-contrib/webpack-bundle-analyzer/tree/e5b617e44df299e7ad4f7dc1bb1cac41e204648c#size-definitions It looks like it's showing `stat` | `gzip`, but it would be awesome to show `parsed`!

came to the issue tracker just for this! let us know if we can help

Sure, I'll send one later.I have an easy repro. The tldr is, Test a component with >1 asynchronous use effect/setState calls (very common). Run test, test passes. Add an afterEach...

Consider this basic `` you are integration testing. This is a very simple, MVP example app: ```tsx // fake api call const getData = (numRecords: number) => sleep(numRecords).then(() => numRecords);...

Definitely. I didn't even see that pure was an option. I certainly wouldn't shift the imports--it was done only to demonstrate the significance of order and async afterEach impact

Anyway, integration testing is prone to regular act() warnings if this isn't considered.

No, I did not. One day I may look deeper, but not soon

if there's an issue for SSG to subscribe to... i'd love to subscribe! i just re-created a small app in aleph "knowing" it supported SSG, only find this issue!

I have a suspicion that text inputs are modeled as controlled fields, which creates unnecessary work on every key stroke .