> all in one js bundle, but if i have http2 then i don’t care because the overhead of multiple files is gone I think everyone who makes this statement has not

> all in one js bundle, but if i have http2 then i don’t care because the overhead of multiple files is gone I think everyone who makes this statement has not tried this. While it is somewhat true for A->B, A->C if not using compression it is definitely not true for A->B, B->C. The deeper your chain is (regardless of if it is within the same package or within different) the overhead of fetching, parsing, building dependency map, fetching dependencies, repeat is pretty huge. I say this as someone that has deployed both approaches at scale and A/B tested them. The benefits of compression should not be understated either. You probably have many repeated things in your files that can be efficiently compressed. Even small stuff like `<div` or `useState` can make a huge difference when you consider them over a larger codebase. This part could have been fixed with SDCH, but only chrome and linkedin seemed to care about that before it was deprecated and removed.