eslint-watch doesn't work with docker-compose

I have been trying to get my front-end working on docker for the past day and I have narrowed down some irregular behaviour to eslint-watch and docker.

I have recreated a minimal working repo of the bug I am experiencing.

It seems that linting is somehow staggered when using docker-compose (docker-compose up specifically, docker-compose run seems to work fine). Rather the last console log statements are staggered. I am not sure what it is, but from my reading the best interpretation I can give is that the log messages that should be printed out for the linting are for some reason not flushed out of the node message queue.

I have narrowed down the message printing to the eslint watcher file. If I add in more console logs at the end of this method it prints out the linting fine, but it staggers my logs (i.e. the last logs in execution).

To replicate, download my repo, run docker-compose up and edit the test.js file and save. You will see what I mean.

I hope this is descriptive enough, it’s a really strange bug.

Any ideas how I can actually figure this out?

[rizowski]

Haha I was using iTerm 2 v3.0.12 to test it out. Glad you were able to figure out the issue. Strange that it was the terminal causing the issue.

[rizowski]

Hey @ryannealmes I am just getting set up for the day. I’ll take a look at it in a few minutes and tell you what I think. Thanks for posting this.