Fonger

We face the same pain too. I think first we shoud mark this repo deprecated on npm to prevent others from using it.

+1

> Thanks, could you address the merge conflict? Sure. I just solved the merge conflict

@balazsorban44 any update?

Crypto Arsenal, using it in all of our forms and strategy code editor https://www.crypto-arsenal.io/ 

@danielgindi I agree with you. 1. Cloudflare, the largest CDN in the world, prioritizes brotli over gzip at server-side. 2. [koa-compress](https://github.com/koajs/compress) has recently added brotli support and they prioritize brotli...

@dougwilson Yes If I see accept-encoding `gzip, defalte, br`, which is what modern browsers currently use, this middleware should use `br` instead of `gzip`. And that is how `koa-compression` does.

IMO, I think quality indicators support can be released in the upcoming version because most browser does not use it for this moment.

Yeah. You're right and I find koa-compress also support quality indicator. We should always follow the standard.

> I guess you could use kubectl wait, then do kubectl logs after that. > > Would something like this work? > > `kubectl apply -f foo.yaml && kubectl wait...