Compressor are of limited use

[awerlang]

Beyond compressing to standard Accept-Encoding values, what else can they be used for?

My use case:

1. Take each asset
2. a few more static files based on a condition
3. then produce a zip file

Current compressor API doesn't make it possible to get to step 2 due to lack of access to current target options. Also, there's assets that won't produce zip files at all (browser code).

I resorted to the Parcel API which listen to build events and generate zip files the way we need.

To be clear: I'm not calling them useless, I state in the first paragraph they have a use, but I wonder if it can be expanded. Or maybe my workaround is the expected way to handle this?

If the compressor API were to be expanded, it needs access to:

• current target (node, browser, entry name, everything)

What are your opinions on this?