João Mota

I will take a look. I just need to understand how the flow server works. Maybe trying to start a flow server ahead of time can help... [eslint-plugin-flow-check does that...

> I am working on project A (`/path/a`), start `npm run lint`. This plugin starts flow server and validates source files. Then I decide to not work on this project...

> They actually stay open In my case, they seem to close... Maybe because I'm on Windows?... Anyway, how do we kill the processes after a certain time period? Can...

Yes. But, that json file you mentioned before; it will only help close processes from previous projects, and it would require someone to run eslint again so that we can...

On the flow documentation I saw that there is a `--from` argument that you can give. Do you think it can be useful to us? Maybe flow is able to...

Maybe we could add a setting like `stopOnExit`, and if it is true, we do ```js process.on('exit', () => childProcess.spawnSync(getFlowBin(), ['stop'])); ``` I think it would be good, at least...

Can you try to run `flow` directly in CI? Without using `eslint-plugin-flowtype-errors`? Thanks

 That is weird. Not sure why we output "Cannot resolve module" but flow passes with no errors... I think it is worth to investigate.

I guess we should use something like `find-up` to find the correct `.flowconfig` instead of assuming that there is only one config file, on the root or in `flowDir`... https://github.com/amilajack/eslint-plugin-flowtype-errors/blob/d765ab242c2de19a6bffff143b87ffc7ba566353/src/index.js#L33-L44...

When you get the error `Invalid position given by 'flowtype-errors/show-errors'. See the description for details. Click the URL to open a new issue!`. What is the description that is given?...