This was a silly oversight on my part. I'd made it so that we suspend the worker and hibernate when the worker reports it failed to lint a file because of a lack of an .eslintrc. But that can happen when you're editing a non-project file, like your own Atom init-file.
So if the no-config error came from a non-project file, we should ignore it.
While I was at it, I made it so that we report a reason in the console whenever we suspend.
This was a silly oversight on my part. I'd made it so that we suspend the worker and hibernate when the worker reports it failed to lint a file because of a lack of an
.eslintrc. But that can happen when you're editing a non-project file, like your own Atom init-file.So if the no-config error came from a non-project file, we should ignore it.
While I was at it, I made it so that we report a reason in the console whenever we suspend.