Update layout.jade
prevent incorrect automatic OPTIONS responses

The router has automatic handling of OPTIONS based on the registered
routes, but if you make an OPTIONS request for an endpoint that does
not exist, then it will still return a 200 with nothing allowed.
Instead, we can let the request move on down the middleware chain. This
has two benefits: first, if the route was not defined and no other
middleware handles it, it will return with a 404. Secondly, if multiple
routers are used and a later one has the route or a custom OPTIONS
defined, the first router will not respond incorrectly.
3.4.8
backport dependency updates

- range parser 1.0.0
- fresh 0.2.1
- send 0.2.0
- cookie-signature 1.0.3
- merge-descriptors 0.0.2
bump deps
3.5.0
pin down less-middleware

Things are broken in 0.2 version of less-middleware so use 0.1 line
3.5.1
some code cleanup
Merge pull request #2004 from agchou/clean-up-code

some code clean up
clean up code consistency
Merge pull request #2008 from agchou/clean-up-code

some code clean up
Tell me what I'm using that isn't allowed

I'm migrating and it would be useful in a large application to know what I'm using that's not allowed. I think lots of people would feel this way. Let me know if you would prefer a different implementation.
Merge pull request #2013 from kentcdodds/patch-1

Tell me what I'm using that isn't allowed
Not work..

This example does not work with express 4.x.
bodyParser() does not have multipart() anymore.
Multiparty module and middleware are added.
Merge pull request #2018 from Devrama/patch-1

This example does not work with express 4.x.
Use SVG badges in Readme
Merge pull request #2025 from seanlinsley/patch-1

Use SVG badges in Readme
handle thrown errors inside Route

close #2029
4.0.0