Maximilian Antoni

Thanks for reporting. Can you please check if this was fixed with #280 in `v13.1.1`?

This is probably obsolete with the new major `v14.0.0` (see #294). Should you're still having the issue, please write here and I'm happy to re-open.

I gave this some thought, and I think you can probably get away with a simpler solution: Instead of introducing "book-keeping" for clients, we could add a command to "flush"...

Awesome! I'm not aware of anyone working on this yet. Let me know if you have any questions. ❤️

This has been addressed with the new major `v14.0.0` (see #294). You can now use `ESLINT_D_PPID` to bind the daemon to your editor process.

Usually this kind of error can be fixed with `eslint_d restart`. Have you tried?

@camin-mccluskey It's actually mentioned here: https://github.com/mantoni/eslint_d.js#what-if-eslint-or-a-plugin-is-updated. If you have ideas how to make that more clear, please feel free to suggest.

This is probably obsolete with the new major `v14.0.0` (see #294). Should you're still having the issue, please write here and I'm happy to re-open.

Thanks for reporting. I made #87 quite some time ago since I had trouble fixing issues myself. It would be great to get some help implementing something like this.

This is probably obsolete with the new major `v14.0.0` (see #294). Should you're still having the issue, please write here and I'm happy to re-open.