Explore replacing express with fastify in dev server

Is your feature request related to a problem? Please describe Serving content via http2 is beneficial and greatly improves load times when serving many files. This is the case when using using a no-bundler such as the builder-vite plugin

When using builder-vite, file count can easily exceed 1k files. This causes load times to be 🐌 . We can alleviate this by enabling http2 when appropriate.

Describe the solution you’d like When running storybook with https enabled:

# optionally we can also autogenerate the selfsigned cert
# maybe take inspiration from the selfsigned package on npm
start-storybook --https --ssl-cert selfsigned.crt --ssl-key selfsigned.key

storybook assets are served via http2

Describe alternatives you’ve considered Accept http1.1 bottleneck

Are you able to assist to bring the feature to reality? yes, I can…

Additional context

[IanVS]

Status update: I had fastify working briefly, before rebasing onto the latest next which now uses tsup, which I’m having some problems with. I’ve pushed up a WIP branch: https://github.com/storybookjs/storybook/tree/fastify. There’s more that needs to be done, but until I can figure out how to deal with errors I’m getting from https://github.com/egoist/tsup/issues/14, I’m a bit stuck. The fastify-webpack-hot issue turned out to be solved, though, since in the new branch we’re not running multiple versions of webpack at the same time, now that the manager is pre-bundled.

[IanVS]

Awesome, thanks! I think if nothing else, it would set us up well for http3/quic, which does appear to have real perf benefits and seems to be getting some activity in node. And fastify will likely add support much faster than express, given the relative pace of development between the two. So yeah, in my opinion this is a good exploration regardless of http2 perf.