node adaptor does not serve contents with any compression

[samccone]

By default the node adaptor should compress responses, right now it does not. Compared to sapper this is a regression.

[benmccann]

brotli might be better yet

[benmccann]

When I run npm run start I also see that all my static assets are being served via http/1.1. http/2 would be preferred though may be difficult to use since it requires https private key and cert. Maybe it's just easier to leave it as http/1.1 for now and do http/2 to the load balancer

[benmccann]

Sapper used Polka/Express. There's half a dozen open PRs there for brotli support: https://github.com/expressjs/compression/pulls?q=brotli+is%3Apr+is%3Aopen+. We might have to wait on that and just do gzip for now

Though Kit uses the built-in Node server. But I'm not sure if we should stick with it since we'd need to figure out how to cache the response after compressing it. https://nodejs.org/api/zlib.html#zlib_compressing_http_requests_and_responses

[GrygrFlzr]

If it's switched to using Express/Polka, should the adapter name be changed to match? It could reduce confusion with regards to required runtime dependencies of the adapted output.