Events not fired properly about meddleware HOT 5 CLOSED

the middleware:before and middleware:after events correspond to when middleware is registered, not when it is loaded into memory or when the factory is run (both of those will happen before the before events). In other words, let's say we have a middleware called custom. You can expect middleware:before (and middleware:before:custom) to fire, then app.use(custom) (or similar), then middleware:after (and middleware:after:custom).

You can see this behavior if you log out the express:router debug statements. For a small sample:

// ---------- index.js ----------
var meddleware = require('meddleware');
var express = require('express');
var app = express();

var config = {
  custom: {
    module: './custom'
  }
};

app.on('middleware:before:custom', function (evt) {
  console.log('before %s ...', evt.config.name);
});

app.on('middleware:after:custom', function (evt) {
  console.log('after %s ...', evt.config.name);
});

app.use(meddleware(config));

// ---------- custom.js ----------
module.exports = function customFactory() {
  return function custom(req, res, next) { next(); };
};

starting the above with DEBUG=express:router node index.js will print out:

before custom ...
  express:router use / custom +5ms
after custom ...

from meddleware.

Hmmm... Ok. Thanks for in-depth example, really appreciated.
Too bad though, i was trying to inject arguments not config related using the events. Makes sense now.
Will try a different approach!
Good work guys!

from meddleware.

Hmm.. if you wouldn't mind walking me through a more specific example, maybe there's another pattern we can tease out that will work for you?

from meddleware.

Well, it's pretty simple: the process is to rig express apps with middlewares, either from modules and local, and they may require different parameters, with no pattern whatsoever. I'm looking at shortstop, looks pretty nice. Also, the config example in this module uses "path:./lib/middleware/example.js" but without shortstop the path is not resolved, right?
Thanks for the help o/

from meddleware.

I'd also checkout confit to do environment-specific (or really anything specific) configs. In fact, that's precisely how we do it with kraken-js.

Thanks for the heads-up on the example. You're right, that shouldn't be in there.

from meddleware.