We are only using one rule at this point: no-callback-literal.

Couldn’t we replace it with handle-callback-err?

I would also like to say that this looks like an old JavaScript coding pattern that can be replaced by promises and async functions.

handle-callback-err is about ensuring that the error is always handled in node.js-style callbacks. E.g. this is an error:

function loadData (err, data) {
    doSomething()
}

no-callback-literal ensures that when a node.js-style callback is actually called, the first argument is always null, undefined, or an Error object. E.g. this is an error:

cb('an error string')

I opened an issue asking if ESLint wants to adopt no-callback-literal so we can deprecate eslint-plugin-standard: mysticatea/eslint-plugin-node#178

I was able to PR the no-callback-literal rule into the eslint-plugin-node project: mysticatea/eslint-plugin-node#179

So, we can close this issue in standard 15 now :)

Posted a request to deprecate eslint-plugin-standard as a follow up to this thread: standard/eslint-plugin-standard#38

@voxpelli I agree. Just released eslint-plugin-standard 5.0.0 and deprecated it.

@feross This package is still listed as a peerDependency for https://github.com/standard/eslint-config-standard-with-typescript thought. So, basically still used.

@sQVe That peerDependency should be locked to 4.x then, or better, replaced there as well

@voxpelli thank you very much for the detailed explanation! 👍

We were still using in our .eslintrc file the standard/* rules defined in the deprecated eslint-plugin-standard

I just replaced these old rules with the ones in the eslint-config-standard rules file and is working good now!