[nwienert]

Does http2 solve waterfall imports? Also wouldn't tree shaking still be unsolved? What about minification?

IMO build step woes are really overstated, my build step has linting, type checking, optimization, bundle analysis size diff checks, enables JSX, and is basically necessary for development anyway as you get hot reloading, compiler-added features for better debugging, etc.

[mixedCase]

>Does http2 solve waterfall imports?

It used to, but browsers ruined it because they didn't want to help improve caching support

[tomjen3]

HTTP2 allows the server to push files to the browser.

If you don't have tons of code, tree shaking and minification is not that important. If you depend on a couple libraries (Jquery, for example) those can be minified and just refered to directly in the source.

[spiffytech]

Chrome removed support for HTTP/2 Server Push last year.

As I remember, it never saw broad adoption because it was technically challenging to integrate with, and it tended to push a lot of resources clients already had, so it wasn't a big win for efficiency anyway.

[semiquaver]

HTTP early hints still exists and can achieve similar things as server push without wasting bandwidth.

[ryncewynd]

Care to share your build set up? I'd very much appreciate it

I haven't done js since jquery days, but keen to get into modern js development

[nwienert]

I maintain Tamagui, so the tamagui starter kit basically is it, try `npm create tamagui`

[semiquaver]

Waterfall imports are solved by rel=modulepreload.