Bundle dashboard assets

[redstonekasi]

Dashboard assets are bundled during startup using esbuild and served from cache.
This approach does not introduce an additional build step, keeping the installation process the same as usual.

Bundling and serving all our own dependencies has two main benefits:

• Everything can be downloaded over one connection.
• Previously, the dashboard needed over 600 requests to load, due to the nature of the date-fns package and esm.sh's behaviour. This is no longer the case.

Prior caching behaviour is maintained by moving the dynamic state into an inline script in the main HTML file. Scripts and fonts are cached for a long time.

I'm not dead set on getting this merged, but I think it does improve things overall.

[yellowsink]

Previously, the dashboard needed over 600 requests to load, due to the nature of the date-fns package and esm.sh's behaviour. This is no longer the case.

can you not combine ?exports with ?bundle? these options would make esm.sh bundle all files and tree shake that server side.

[yellowsink]

I did this for plot so I'm surprised I didn't for date fns

[yellowsink]

oh shit I did did I just forget the ?bundle

[redstonekasi]

can you not combine ?exports with ?bundle? these options would make esm.sh bundle all files and tree shake that server side.

Nope, that doesn't work. They've since shuffled flags around a bit, but regardless, they don't support bundling things in cases like date-fns where every function receives its own export. Doing so could subtly break things is their reasoning, they're not wrong, but in this case that isn't the case of course.

[yellowsink]

:( ok fair