updated phantomjs dependency. closes #26
0.2.1
Updated README fixed example code - closes gh-32

there was lots of extra `,`'s
Wrap bridge.js in a function to keep from polluting global name space. Closes GH-33.
Adding failure condition upon no tests run in a single test module/file instead of only on a qunit test target
Switching to spaces instead of newlines for clickable URLs. Closes GH-30.
Update copyright
Update devDeps
Remove broken link in docs
Bump v0.2.2
Add new events for fail conditions, so that reporters can still report on the test
Update QUnit to latest; cleanup QUnit markup
Add `force` option

When force is true, upon completion of all tests, test failures will not
cause the whole task to fail, in either the case of a negative
assertion, or when there were no assertions at all. This can be set to
true when you always want other tasks in the queue to be executed.

This is effectively implements --force at a task-specific level, where
it is common to want to continue even when tests fail.

Certain PhantomJS error conditions have also been changed to raise test
failures rather than exiting the task immediately.
Cleanup trailing whitespace in docs
Revert "Cleanup trailing whitespace in docs". Necessary for hard linebreaks.

This reverts commit 72feaff50c9393bd390be96df89bcb759772ba8e.
Update readme to document PhantomJS OS dependencies. Fixes #43
Update README
Propagate error.onError events from Phantom. Closes GH-11.

They can then be handled in Gruntfile.js using
grunt.event.on('qunit.error.onError', function (msg, stack) { ... })
removing confusing error message
Remove Gruntfile.js as main in package.json