Okay, so when using the killFlow option, it takes about 5s to run the task for me, every time. When not using that option, it takes 5s to run the first time and then around 500-800ms every time after that
Let me modify the readme
Can you help me with the tests?
@josebalius squashed :thumbsup:
@charliedowler awesome, thanks! I'll submit a PR for the beep shortly with a beep flag.
Thanks for your contributions
does npm run lint work ok for you?
▶ npm run lint
> email@example.com lint /Users/jgarcia/Sites/gulp-flowtype
> jshint **.js && flow check --lib ./declarations/
Found 0 errors
@charliedowler I use up-to-date version of gulp-flowtype, it's awesome! Although, sometimes it's more convenient to get help from built-in text-editor support. Gulp-flowtype mostly used for a prebuild task at CI
Anyone knows if it makes sense to use Flow in conjunction with JSHint? Is Flow a replacement for JSHint?
@helpermethod from my understanding, you would use JSHint & Flow as two separate tools. Flow is not a replacement for JSHint, JSHint is for code quality rather than type checking. Hope that helps
@unknownexception Remember that error handling you added? Would it be better to throw a gulp error instead of logging it out as if it were a flow error? The current way makes it harder to differentiate at a glance what type of issue it is.
@charliedowler sure, It makes sense. Sorry for not responding, I'm going to enable notifications to gitter.
is this chat still active? :D
Still here, not getting any notifications though... Anything I can help you with @clooth ?
Hey @all! Are there any plans to update flow-bin dep to 0.16.x?