Trying to figure out why eslint-watch doesn't work with docker-compose correctly -

i have been trying front-end working on docker past day , have narrowed down irregular behaviour eslint-watch , docker. have recreated minimal working repo of bug experiencing.

it seems linting somehow staggered when using docker-compose (docker-compose up specifically, docker-compose run seems work fine). rather last console log statements staggered. not sure is, reading best interpretation can give log messages should printed out linting reason not flushed out of node message queue.

i have narrowed down message printing eslint watcher file. if add in more console logs @ end of method prints out linting fine, staggers logs (i.e. last logs in execution). funny thing is, if save again flushes rest of message queue i.e. previous logs print out.

to replicate, download repo, run docker-compose up , edit test.js file , save. watch logs in terminal linting. see mean.

i hope descriptive enough, it's strange bug , difficult explain in question.

any ideas how can figure out?

finally figured out. iterm of things culprit. weird.

anyway using iterm2 3.0.9. seems in iterm2 3.0.12 (os 10.8+) bug fixed.

https://github.com/rizowski/eslint-watch/issues/94#issuecomment-261287265