Leaflet.buffer icon indicating copy to clipboard operation
Leaflet.buffer copied to clipboard

Update eslint-import-resolver-webpack to the latest version ๐Ÿš€

Open greenkeeper[bot] opened this issue 7 years ago โ€ข 6 comments

โ˜๏ธ 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. If those donโ€™t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot :palm_tree:

greenkeeper[bot] avatar Mar 30 '18 10:03 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] avatar May 17 '18 11:05 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.

greenkeeper[bot] avatar Jun 24 '18 17:06 greenkeeper[bot]

Update to this version instead ๐Ÿš€

Release Notes for custom resolvers!

Resolver plugins: now the linter can read Webpack config, properly follow aliases and ignore externals, dismisses inline loaders, etc. etc.!

greenkeeper[bot] avatar Jan 22 '19 19:01 greenkeeper[bot]

Update to this version instead ๐Ÿš€

greenkeeper[bot] avatar Apr 13 '19 07:04 greenkeeper[bot]

Update to this version instead ๐Ÿš€

greenkeeper[bot] avatar Dec 08 '19 07:12 greenkeeper[bot]

Update to this version instead ๐Ÿš€

greenkeeper[bot] avatar Jan 11 '20 07:01 greenkeeper[bot]