TJ
TJ
we could implement it as more middleware that get injected inbetween, so you'd just do a normal `yield`. it feels super dirty to do this at the `compose` level though,...
we should probably add regular toJSON support, that could be used
maybe something better would be to just add a simple hook for stuff like this, then any could be used
we should change it anyway, it should be `require('express-expose')(app)`
yeah, definitely, I wouldn't mind getting that in, I suppose at that point it becomes more like browserify so it might be better to keep express-expose for small request specific...
i haven't used browserify. im generally not a fan of magical scripts since it's not necessarily obvious where they were generated, but might be something worth adding some day
seems to also not degrade properly, menu doesn't work on my phone
I think you'd have to [filter on the branches](https://github.com/actions/bin/tree/master/filter) you want, then create two different deployment actions in order to tweak config
ah damn, that's kind of lame, otherwise yeah you could have two concurrent filters for the two branches and do it that way, hmm... haha