Event batcher for gulp-watch'er.
This is problem solver for this issue with gulp.watch and gulp-mocha.
Long story short - example below without
batch'ing will call mocha as many times, as many files was changed (for example
git checkout can touch dozens files).
Also it can be used with
gulp-watch to provide batching callback handler, instead of streaming events from gaze.
Main purpose for this module is running tests in
gulp-watch. So here it is:
var gulp = ;var batch = ;gulp;
This function creates batcher for provided callback.
It will call it, when bunch of events happens near in time, so you will
be running your test only once per
git checkout command (for example).
Streamof incoming events.
done- is callback for your function signal to batch, that you are done. This allows to run your callback as soon as previous end. Error can be passed as argument.
limit- Maximum events number, that gets into one batch (default:
timeout- Interval in milliseconds, that counts as "no more events will arrive" (default:
All errors in batched function will be passed to
Wrapped callback, that will gather events and call callback.
Copyright (c) 2013 Vsevolod Strukchinsky (email@example.com)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.