You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that after closing all the clients that talk to eslint_d, the server keeps running with significant memory usage.
It would be good to have the ability to optionally register a client when talking with eslint_d for the first time. The daemon could keep a list of all clients that are connected. When a client notifies that wants to disconnect, the daemon will check if it's the last one connected and then stop itself.
could this be considered a feature to implement?
The text was updated successfully, but these errors were encountered:
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" or "evict" a cached instance.
Instances are internally associated with a working directory, so a command like eslint_d evict . could remove the cached instance for the project in the current directory. You can then trigger that command when your editor exits.
Would you be interested in contributing this feature?
I have noticed that after closing all the clients that talk to eslint_d, the server keeps running with significant memory usage.
It would be good to have the ability to optionally register a client when talking with eslint_d for the first time. The daemon could keep a list of all clients that are connected. When a client notifies that wants to disconnect, the daemon will check if it's the last one connected and then stop itself.
could this be considered a feature to implement?
The text was updated successfully, but these errors were encountered: