Upgrade jsx-ast-utils to support Optional Chaining

[junoatwork]

I opened an issue upstream on jsx-ast-utils: jsx-eslint/jsx-ast-utils#103 , which was fixed in [email protected]

Symptom:

Began seeing The prop value with an expression type of ChainExpression could not be resolved. Please file issue to get this fixed immediately. in eslint output after upgrading.

ECMAscript Optional Chaining shipped, resulting in various changes to parsers and javascript/typescript tools to support it. Initially there were different, non-standard names for the AST nodes to represent it. Over this year, consensus has settled out, including in the parser that eslint uses, estree (see estree/estree#204 ).

Versions:

[email protected]
[email protected] (via [email protected], [email protected])

Minimal test case

Component.jsx

import React from 'react';

export function Component() {
  const x = {};
  return (
    <div role="button" key={x.y?.z}>
      hi
    </div>
  );
}

.eslintrc

module.exports = {
  extends: [
    'plugin:react/recommended',
    'plugin:jsx-a11y/recommended'
  ],
  plugins: ['react', 'jsx-a11y'],
}

run

eslint ./Component.jsx

[ljharb]

The next patch release of eslint-plugin-react will include jsx-ast-utils v3.