I was thinking about deprecating the cache buster feature in v4 since I'm sure there are more robust, dedicated tools for that which can be used in conjunction with bless.
The goal of bless has always been to split a CSS file into the optimal size based on the number of selectors.
Cache buster was something that got added for convenience along the way but it distracts from the purpose of the tool and couples bless to a different problem.
Original discussion here: https://github.com/paulyoung/bless.js/pull/32#issuecomment-62604442
There have been a lot of pull requests/issues about this, and people have opinions. I'd like to track this here.