migrate to neostandard / eslint-config-express

[ctcpip]

besides, semi, @stylistic/space-before-function-paren is the only rule added and that is because it is the style that express uses today so we should keep it

[bjohansebas]

In case the ESLint configuration in Express is managed by a package created by a member of the organization, it might be better to handle it with the @express scope on npm (after resolving the discussion about the linter).

[bjohansebas]

Given that standard/semistandard don't want to update to the latest version of ESLint, +1 on using neostandard.

[voxpelli]

import neostandard from 'neostandard'; export default neostandard({ semi: true, // Enforce semicolons (like semistandard) });

neostandard supports semistandard style out of the box, so only the one override of that space before function parentheses would be needed, though it should be done by Reyes if the same plugin that neostandard exports itself, not one it imports itself, as else there may be nasty errors in some scenarios (ESLint defiling algorithm)