static serve page lacks in directions beyond the readFile usage and can definitely be improved

[nopeless]

https://h3.unjs.io/examples/serve-static-assets

Shows an example but uses readFile which itself is bad because it loads the entire file in memory.

The page doesn't show any other direction to the reader if they want to avoid using readFile or intend to serve partial content especially for videos.

For comparison, express.static has partial content support, and doesn't load the entire file in memory as well. (vercel's serve-handler also does this but it has been pretty stale)

I'm not sure what you intend with the page but here are some solutions in my head

• mark the page as "not production use"
• explain the performance pitfalls of the implementation
• direct readers to other middlewares for partial or memory friendly implementations of static serving