lineman grunt spec-e2e. :+1:?
oops.
screw this, use firefox
get protractor happy with coffeescript

* the grunt task runs the cli in-process now so
that I can require("coffee-script")
* conveniently making it an async grunt process
goes well with the fact that protractor exits the
process on your behalf (ugh + yay!)
* comment out the chromedriver location since it
should be on folks' PATH anyway
switch to jasmine-given
Merge pull request #7 from testdouble/master

lineman grunt spec-e2e. :+1:?
updates jasmine-given to the real one
Fixes jasmine-given path
Adds coffee-script dependency
Reverts to chrome for e2e specs

If you have issues with Chrome, `brew upgrade chromedriver`
updates to angular 1.2.0-rc.2
Updates template paths to be less clunky
update helper
Makes the lineman install step better :P
Add needed step in the instructions

fix #10 :)
Merge pull request #11 from Foxandxss/patch-1

Add needed step in the instructions
Upgrade jasmine-given
fix(index.us) - Absolute routes to css and javascript file to allow routes with params

Seems like relative paths to the `app.cs` and `app.js` doesn't work if you have routes with params like `/foo/:id`. Both `ngRoute` and `ui-router`.

Cheers.
Merge pull request #13 from Foxandxss/patch-1

fix(index.us) - Absolute routes to css and javascript
Let npm update protractor with new versions

I think that protractor is one of those dependencies that doesn't hurt to have at the last version because it is just in its early stages with a lot of bugs (@searls knows what I am talking about :P).

TL;DR; I think that having protractor in the last version doesn't hurt. Feel free to change it to ~0.10.0 or what you want :)