Support watch which re-run tests when files changed

[huang47]

steal @amasad's wisdom from #96

I am still debugging why the default file watcher of sane emit duplicate events every time I make a file change.

[huang47]

seems like a regression of nodejs/node-v0.x-archive#2126
by using watchman there is no such issue

[cpojer]

why did you add this back? :)

[huang47]

npm i --save which order the dependencies alphabetically.

[cpojer]

got it, please remove Bluebird – we are not using it any more :)

[amasad]

@huang47 perfect! Followups:

• Can we add this to the documentation/website?
• Future improvements: only run the tests that was affected by the change
• It'd be great, if we can do the same thing for internal jest test runner.

[amasad]

@cpojer should we release a new minor version for this?

[cpojer]

Before publishing this I'd like to add documentation first. @huang47 can you send a pull request for that? :) I think a patch release is fine, based on how we develop jest we have only bumped "minor" versions for breaking changes.

We can also just go back to 5.0.4 and use semver properly, I wouldn't be opposed to that actually – let's discuss internally.

[huang47]

sure, will create another PR to address the document changes.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.