When there's no ESLint config, the error is shown in the buffer, which is an annoying experience when a user is working on JS-related files that are not associated with a config.
We should warn the user of the error once instead of showing the error in the buffer:
Closed #462
When there's no ESLint config, the error is shown in the buffer, which is an annoying experience when a user is working on JS-related files that are not associated with a config.
We should warn the user of the error once instead of showing the error in the buffer: