cowboy/javascript-route-matcher — pull request #2 by virtualandy (2014-12-04 17:01:29+00:00)
Title: Support for bower install & wiredep

@cowboy if you don't want this that's okay. It's probably a small issue.
We're using [wiredep](https://github.com/taptapship/wiredep) via [a grunt plugin](https://github.com/stephenplusplus/grunt-wiredep) that came with the [angular-fullstack-generator](https://github.com/DaftMonk/generator-angular-fullstack) we used to kickstart our app.

After running ```bower install``` and then ```grunt build``` (or **server**, or whatever includes the **wiredep** task), anything listed in our bower.json that includes a 'main' field will get automatically inserted into a section of our html files. So we can have someone run ```bower install``` and magically scripts are in our page. It's sort of handy but not a make-or-break feature.

At any rate, without a bower.json that specifies a main in this package, that wiredep step won't work. So I think I added one + rev'd the version correctly. I think all you will have to do is update/push to github and bower will pick it up.

I did it with [my fork of javascript-route-matcher](https://github.com/virtualandy/javascript-route-matcher) and it seemed to work with wiredep okay. Let me know if this PR needs cleanup or I can help in any other way. Thanks!