dangling comma vs. newline paren in 12.

In eslint-config-airbnb-base version 11.3.0, this was ok:

const addFrameworkSoapHeader = soapClient =>
  soapClient.addSoapHeader(
    { Security: 'wsse' },
    'frameworksecurity',
    'wsse',
    'http://schemas.xmlsoap.org/ws/2002/07/secext');

In version 12.0.0, you get in this circular loop. The above code says parens must be on new line, so it becomes:

...
'http://schemas.xmlsoap.org/ws/2002/07/secext'
);

However, if you do that, you get yelled at for no dangling comma. So if you add that:

...
'http://schemas.xmlsoap.org/ws/2002/07/secext',
);

Then ESLint abandons the whole file because of a parsing issue with the extra paren:

Parsing error: Unexpected token )

For now, we’ve locked version in our package.json to 11.3.0.

[JesterXL]

@ljharb You rock, thanks man!

[danm]

thanks @ljharb, interesting. I always assumed that your style guide was always opinionated towards modern syntax of ES. So that if these rules are followed, and you use a modern version of Node, it would always work.

Totally understand from the client perspective. I shall add transpiling to my server side work flow from now on!