-
Notifications
You must be signed in to change notification settings - Fork 142
[Feature Request] Command to manually kill and restart worker #1033
Comments
You can clear the module cache by checking then unchecking Disable FileSystem Cache in the Settings. Not as convenient as a Command, and I'm not 100% sure it will work for your case of "thrown ESLint Errors", because those thrown Errors could be fatal. Additionally you can reload the Electron browser window with command |
That setting only clears the cache of searched paths, it has nothing to do with clearing things out of the module cache once they are in there. It's only useful in situations where your file tree changes often. Reloading the Atom window or deactivating/reactivating the package is the only current way to restart the worker process. |
BTW, I could still use this (kind of). And @skylize, reloading the window repeatedly gets old real fast. You lose things like undo/redo, etc. when you do that, for example. (And when diagnosing problems with |
It'd be hugely convenient when working on rules, especially local ones via
eslint-plugin-local
oreslint-plugin-rulesdir
, or newly reinstalled ones, to be able to kill and restart the worker process manually. That way, the module cache could be cleared and repopulated, which keeps me from having to restart Atom entirely over thrown ESLint errors.The text was updated successfully, but these errors were encountered: