fix: walk invalidated dependencies

[tivac]

Description

When invalidation was added in #532 I apparently forgot to account for it withiin the dependency walking code, so invalidated files wouldn't ever be rewalked.

Motivation and Context

This has likely been causing a variety of nasty-to-debug errors in the wild 😞

How Has This Been Tested?

See #572, the added test in watch.test.js is how I discovered this was broken.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[tivac]

This should also help with #571 and I think in combination with #574 that problem should be solved, I'll leave it open until I've given it some time to bake though.

[TravisBuddy]

Hey @tivac,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: 44953520-5130-11e9-977c-5d859f4a0935