Maximilian Antoni

Thank you for reporting and also providing a solution! 😍 A potential solution to this could be the idea to launch a separate process per project [as suggested here](https://github.com/mantoni/eslint_d.js/issues/264#issuecomment-1807650596), which...

> I would be in favor of separate processes. I do wonder if this may cause excessive instances in some situations. Separate instances could also make the proposed solution for...

Thanks for sharing your thoughts, @higherorderfunctor. - The TTL idea could be opt-in, either with an option to `eslint_d start` or another environment variable. - I don't see how building...

This is obsolete with the new major `v14.0.0` (see #294). The new release supports eslint v9 and leaves config detection to eslint itself. You should be able to use `eslint_d`...

There's a pending issue for this feature: #87

Unfortunately the `--fix-to-stdout` option had to be removed with `v14.0.0` and I'm not intending to bring this back due to the way the new implementation works. Sorry.

@uloco Thanks for offering help. This will need test cases and the validation should happen when starting the server so that we can log to stderr or fail. Currently this...

This is obsolete with the new major `v14.0.0` (see #294). The new release spawns a separate instance per eslint installation. Please see the README on how to control the lifetime...

I have no experience publishing anything to homebrew. Would you be able to assist with setting this up? And most importantly, can you contribute a script that automates the publishing...

I just released `v6.1.0` with a change from @amritk which adds a debug flag to log child process output to the console (see #27). Does this help with your issue?