Closed lukasoppermann closed 7 years ago
Does this also happen when running standard from the command line? Also, could you post the output of npm ls eslint
?
It seems to have been fixed with the latest update.
@sonicdoe This is still possible.
The problem looks to be that if there was an error thrown in a lintPromise
, undefined
will be returned as the .catch()
block has no return statement.
I'd recommend returning null
so that linter
will simply keep it's current cache of messages for the provider (if it has any).
@Arcanemagus Thanks 👍 Fixed in https://github.com/ricardofbarros/linter-js-standard/commit/32e8b7507b53eb56abc71e999892de813dd560c2.
Hey I am getting this error:
as well as
I've got
standard 10.0.2
installed in my repo andlinter-js-standard@3.9.0
. Any idea why this happens? It happens every time I save the file or write anything (so whenever the linter runs).Thanks.