Update eslint-import-resolver-webpack to the latest version 🚀

[greenkeeper[bot]]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.9.0 of eslint-import-resolver-webpack was just published.

Dependency	eslint-import-resolver-webpack
Current Version	0.8.4
Type	devDependency

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

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of eslint-import-resolver-webpack.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper bot :palm_tree:

[greenkeeper[bot]]

Version 0.10.0 just got published.

Update to this version instead 🚀

Release Notes

errors abound

Breaking: removed no-errors rule. Instead, each individual rule will report parse errors in the target imported file, if encountered.

#90: Added {commonjs: [bool], amd: [bool]} option object to no-unresolved. If set true, will attempt to resolve module paths for CommonJS require and AMD define + require in a limited set of cases. Not nearly so smart as Webpack, but smart enough to be useful. (hopefully.) Thanks @mctep for changing my mind on this. 😁

#94: Dependency parser will infer 'jsx' plugin if using default Babylon and jsx is asserted in the ecmaFeatures. Thanks @jameslnewell for bringing this up.

#88: un-smarted no-require. It will now report on all require statements, everywhere, regardless of target.

[greenkeeper[bot]]

Version 0.10.1 just got published.

Update to this version instead 🚀

Release Notes

correctness

• cache correctness: should properly re-load changed files even in a long lived process (like a webpack dev server)
• fixed issue where inferring JSX parsing from ecmaFeatures.jsx was broken when ESLint froze the context and settings. My own fault... not very hygienic to mutate shared state in the first place.