Now it needs tests.
Added `@use 'staticGzip'` #45 @imzshh
What about the Compress middleware? http://expressjs.com/api.html#compress
staticGzip only compress static files, while the compress middleware compress all response content.
The docs says you can pass a filter function for specific file types so we can use that. The reason I'm asking is that using compress means less code to maintain, less packages to depend on and zero tests to write :)
As an off topic: Unless it's a weekend project or a prototype I think nginx / apache should serve the static assets, not node.
How about have our cake and eat it: we could leave the staticGzip option but make gzippo a soft dependency -- similar to what we already do for jsdom, less, etc.
I seems that gzippo is dead (which makes sense given compress), and that compress (plus staticCache potentially) is the way to go.
I'll add a deprecation warning for staticGzip and I'm planning to remove that feature in a few versions.
deprecate `staticGzip` (#45)
This is obsolete. staticGzip is deprecated. Can be closed.