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

Bump eslint-import-resolver-webpack from 0.8.3 to 0.9.0 #608

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

Conversation

dependabot-preview[bot]
Copy link

Bumps eslint-import-resolver-webpack from 0.8.3 to 0.9.0.

Changelog

Sourced from eslint-import-resolver-webpack's changelog.

Change Log

All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
This change log adheres to standards from Keep a CHANGELOG.

[Unreleased]

  • Fixer for [first] ([#1046], thanks [fengkfengk])

[2.10.0] - 2018-03-29

Added

  • Autofixer for [order] rule ([#711], thanks [tihonove])
  • Add [no-cycle] rule: reports import cycles.

[2.9.0] - 2018-02-21

Added

[2.8.0] - 2017-10-18

Added

Changed

  • Case-sensitivity checking ignores working directory and ancestors. ([#720] + [#858], thanks [laysent])

Fixed

  • support scoped modules containing hyphens ([#744], thanks [rosswarren])
  • core-modules now resolves files inside declared modules ([#886] / [#891], thanks [mplewis])
  • TypeError for missing AST fields from TypeScript ([#842] / [#944], thanks [alexgorbatchev])

[2.7.0] - 2017-07-06

Changed

  • [no-absolute-path] picks up speed boost, optional AMD support ([#843], thanks [jseminck])

[2.6.1] - 2017-06-29

Fixed

  • update bundled node resolver dependency to latest version

[2.6.0] - 2017-06-23

Changed

  • update tests / peerDeps for ESLint 4.0 compatibility ([#871], thanks [mastilver])
  • [memo-parser] updated to require filePath on parser options as it melts
    down if it's not there, now that this plugin always provides it. (see [#863])

[2.5.0] - 2017-06-22

Re-releasing v[2.4.0] after discovering that the memory leak is isolated to the [memo-parser],
... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot ignore this [minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use [this|these] label[s] will set the current labels as the default for future PRs for this repo and language

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)

Finally, you can contact us by mentioning @dependabot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant