The version 0.10.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.
Release Noteserrors 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.
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).
Coverage remained the same at 100.0% when pulling b0302fedd146a7cb4ba09b5dadac599b7365ec11 on greenkeeper/eslint-import-resolver-webpack-0.10.0 into 72a45a1ede5c2b1f7158d89228006bded3b0090f on master.
Version 0.10.0 of eslint-import-resolver-webpack was just published.
eslint-import-resolver-webpack
The version 0.10.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.
Release Notes
errors aboundBreaking: 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 tono-unresolved
. If settrue
, will attempt to resolve module paths for CommonJSrequire
and AMDdefine
+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 theecmaFeatures
. Thanks @jameslnewell for bringing this up.#88: un-smarted
no-require
. It will now report on allrequire
statements, everywhere, regardless of target.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: