savetheclocktower
commented
2 years ago OK, I implemented the worker-killing after all. I needed JobManager to have a better handle on the worker life-cycle anyway. This lets us defer worker creation until the first linting job, and to go into “sleep mode” eagerly, since we can easily restart the worker if we think we'll need it.
I've also got an interest in reducing how much this package does in projects without ESLint installed, or in windows that aren't even JavaScript projects. Ideally I'd like to kill the worker once it's clear it's not needed, but for now all I'm interested in doing is not sending a job to the worker when we know what the outcome will be.