Added some additional instructions for making it work on Windows
Fix handling of value property on inputs

Fixes #890; fixes #891
Remove nonstandard EventTarget static methods

Fixes #860.
Update all dependencies

Most of these were already floating to the appropriate version, except parse5 and htmlparser2. Regardless, it's good to set a higher minimum to make sure everyone gets the latest, especially of things like Contextify.
Re-format package.json

Let npm manage this formatting from now on.
Version 1.0.0
Run browser tests on SauceLabs in CI
Correct the return value of EventTarget#dispatchEvent.

It appears that the return value of EventTarget#dispatchEvent is intended to be `true` if the default was *not* prevented. That is, `canceled = !target.dispatchEvent(event)`. In every browser I ran the following test and got the same thing, which is the opposite of what jsdom returned before this commit.

    > e = document.createEvent('UIEvents')
    > e.initEvent('keydown', true, true)
    > document.body.dispatchEvent(e)
    true
    > document.body.addEventListener('keydown', function(e){ e.preventDefault() })
    > e = document.createEvent('UIEvents')
    > e.initEvent('keydown', true, true)
    > document.body.dispatchEvent(e)
    false

Looking at the specs, I find evidence for this in the spec for `dispatchEvent`[1], specifically 4.7.13:

> Return false if event's canceled flag is set, and true otherwise

The `canceled` flag is set by `preventDefault()` if `cancelable` is `true`.

Additionally, the web-platform-tests project has a test for
`dispatchEvent` that asserts that the return value is `true` when the
event is not cancelable [2].

[1]: https://dom.spec.whatwg.org/#dom-eventtarget-dispatchevent
[2]: https://github.com/w3c/web-platform-tests/blob/04be7dd98aa106989948ac4e5d9cb7398e6a0d4d/dom/events/EventTarget-dispatchEvent.html#L36
Version 1.0.1
Fix undefined messages in w3c tests

Makes w3c test fail informatively (#895).
Going down the rabbits hole
Rebuild css rules on text node changes