Using :target :esm in dev mode, it seems like the network requests to get all the JS seem to take quite a long time - I see 15s roughly for DOMContentLoaded... The network tab is quite busy with requests set to (pending)
I couldn’t find any reference to ESM not being subject to the http connection limit. Perhaps for faster dev we’d need http2 but it’s a pain
I tried with https/h2 and it seems the loading time is comparable. I switched shadow-cljs and our own server to ssl with a mkcert certificate. Everything worked fine but again the behaviour was the same - a ton of waterfall-like requests in the backlog.
Presumably this is because of the old 6-connections-per-server limit... But we were always using :loader-mode :eval which was still downloading invididual files IIRC?
esm doesn't have the 6 connection limit I think? but :loader-mode does not exist in :esm, it always uses the built-in browser import thing
How many files are we talking? I never much tested this with :esm and just assumed that browser just had addressed these issues 😛
but I guess yeah the server still matters
I can see about making the :eval mode available for :esm