Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency eslint-import-resolver-webpack to v0.12.1 #12

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 21, 2018

This PR contains the following updates:

Package Type Update Change
eslint-import-resolver-webpack devDependencies minor 0.8.3 -> 0.12.1

Release Notes

benmosher/eslint-plugin-import

v0.12.1

Compare Source

Changed
  • Broke docs for rules out into individual files.

v0.12.0

Changed
  • Ignore import/ignore setting if exports are actually found in the parsed module. Does this to support use of jsnext:main in node_modules without the pain of managing an allow list or a nuanced deny list.

v0.11.0

Compare Source

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

v0.10.1

Compare Source

See GitHub release notes
for info on changes for earlier releases.

v0.10.0

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.


Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/eslint-import-resolver-webpack-0.x branch from 7ea2bf9 to 76e0791 Compare January 22, 2019 12:06
@renovate renovate bot changed the title Update dependency eslint-import-resolver-webpack to v0.10.1 Update dependency eslint-import-resolver-webpack to v0.11.0 Jan 22, 2019
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-webpack-0.x branch from 76e0791 to 75f2fe2 Compare April 23, 2019 13:00
@renovate renovate bot changed the title Update dependency eslint-import-resolver-webpack to v0.11.0 Update dependency eslint-import-resolver-webpack to v0.11.1 Apr 23, 2019
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-webpack-0.x branch from 75f2fe2 to b844919 Compare December 14, 2019 18:50
@renovate renovate bot changed the title Update dependency eslint-import-resolver-webpack to v0.11.1 Update dependency eslint-import-resolver-webpack to v0.12.0 Dec 14, 2019
@renovate renovate bot force-pushed the renovate/eslint-import-resolver-webpack-0.x branch from b844919 to dfb0319 Compare January 18, 2020 19:59
@renovate renovate bot changed the title Update dependency eslint-import-resolver-webpack to v0.12.0 Update dependency eslint-import-resolver-webpack to v0.12.1 Jan 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant