v3.0.4

• meddleware deployed outside app's node_module can now resolve app's middleware modules deployed

v3.0.2

Fixes

1. Fix regression for the enabled option inside any of the flow control registration types.

Implementation, Pull Request

v3.0.1

Breaking Changes

1. registered middleware factories are now called with a context set to the method owner. This helps in specific cases (e.g., Passport).
   Previously: The factory was called with a context of null.

   Implementation, Issue, Pull Request

v2.1.0

New Features

1. Add support for the route option to take a regular express. Caveats: with *.json configs, you will still need to convert the string to a regular express with something like shortstop-regex. Additionally, any mountpath will need to be properly accounted for by your regular expression.

   Documentation, Implementation, Pull Request

v2.0.0

Breaking Changes

1. Middleware now defaults enabled to true. I.e., omitting the enabled option will still enable the middleware.
   Previously: middleware was defaulted enabled to false.

   Implementation, Issue, Pull Request

2. The ability to toggle the enabled state of a middleware at arbitrary points during runtime has been removed. Now, a middleware that is not enabled—by explicitly setting enabled to false, given breaking change No.1—will not be required (i.e., not parsed), and cannot be enabled at a later time.
   Previously: middleware could be toggled. Was by design, but largely unused and caused unanticipated behavior.

   Issue, Pull Request

v1.0.0

Initial express 4.x support.