Update jsx-ast-utils to the latest version 🚀

[greenkeeper]

Version 2.0.0 of jsx-ast-utils just got published.

Dependency	jsx-ast-utils
Current Version	1.4.1
Type	dependency

The version 2.0.0 is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of jsx-ast-utils.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

---

Commits

The new version differs by 6 commits.

• 14b3145 2.0.0
• 5a698b8 Update CHANGELOG.
• 25fe686 propName should always return a value (#50)
• bc61ce9 Update README.md
• f84c0b3 Upgrade devDependencies.
• a57b080 Remove all lockfiles. (#44)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[coveralls]

Coverage remained the same at 99.57% when pulling 4ab568a on greenkeeper/jsx-ast-utils-2.0.0 into 469243b on master.

[hammadzz]

There is a bug so this should be updated, I am running into it now:

jsx-eslint/jsx-ast-utils#33

[thibautvs]

Confirmed, I have the same problem:

The prop value with an expression type of BindExpression could not be resolved.
at Object.extract [as JSXExpressionContainer]

Setup to reproduce (essentially every latest version of these packages as of 5th of October 2017):

• react: 16.0.0
• eslint: 4.8.0
• eslint-config-airbnb: 15.1.0
• eslint-plugin-import: 2.7.0
• eslint-plugin-jsx-a11y: 6.0.2
• eslint-plugin-react: 7.4.0

Regards,

Thibaut

[Nantris]

Same issue. jsx-ast-utils v2.0.1 supposedly fixes this issue.

jsx-eslint/jsx-ast-utils#33