fix(deps): update dependency eslint-import-resolver-webpack to v0.10.1 #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://github.com/avatars/in/2740?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request updates dependency eslint-import-resolver-webpack from
v0.8.4tov0.10.1Release Notes
v0.10.1Compare Source
See GitHub release notes
for info on changes for earlier releases.
errors abound
Compare Source
Breaking: removed
no-errorsrule. 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 CommonJSrequireand AMDdefine+requirein 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
jsxis asserted in theecmaFeatures. Thanks @jameslnewell for bringing this up.#88: un-smarted
no-require. It will now report on allrequirestatements, everywhere, regardless of target.v0.9.0Compare Source
This PR has been generated by Renovate Bot.