@drewfish I like this idea overall instead of just tagging onto `app.mojito` namespace! The only thing is that `"store"` is very generic, and I am thinking perhaps a more mojito specific NS should be used. e.g. `app.set('mojito store', mojito.store');`.

For this specific issue here, search team have quite a few mojito-* extensions out there with middleware that relies on `midConfig` being passed to for initialization, and having to delay the initialization until that first request will basically break those. We can provide a level of BC but make sure we document those as _deprecated_ and _not recommented_ for future use, which I think is the least resistant path.