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

chore(deps): update dependency eslint-plugin-import to v2.11.0 #236

Merged
merged 1 commit into from
May 1, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 12, 2018

This Pull Request updates dependency eslint-plugin-import from v2.10.0 to v2.11.0

Release Notes

v2.11.0

Compare Source

Added
Fixed

2.10.0 - 2018-03-29

Added

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

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 v2.4.0 after discovering that the memory leak is isolated to the memo-parser,
which is more or less experimental anyway.

Added
  • Autofixer for newline-after-import. (#​686 + #​696, thanks @​eelyafi)

2.4.0 - 2017-06-02 [YANKED]

Yanked due to critical issue in eslint-module-utils with cache key resulting from #​839.

Added

2.3.0 - 2017-05-18

Added
Changed
Fixed
  • attempt to fix crash in no-mutable-exports. (#​660)
  • "default is a reserved keyword" in no-maned-default tests by locking down babylon to 6.15.0 (#​756, thanks @​gmathieu)
  • support scoped modules containing non word characters

2.2.0 - 2016-11-07

Fixed
  • Corrected a few gaffs in the auto-ignore logic to fix major performance issues
    with projects that did not explicitly ignore node_modules. (#​654)
  • import/ignore setting was only being respected if the ignored module didn't start with
    an import or export JS statement
  • prefer-default-export: fixed crash on export extensions (#​653)

2.1.0 - 2016-11-02

Added
Fixed

2.0.1 - 2016-10-06

Fixed
  • Fixed code that relied on removed dependencies. (#​604)

2.0.0! - 2016-09-30

Added
  • unambiguous rule: report modules that are not unambiguously ES modules.
  • recommended shared config. Roughly errors and warnings mixed together,
    with some parserOptions in the mix. (#​402)
  • react shared config: added jsx: true to parserOptions.ecmaFeatures.
  • Added no-webpack-loader-syntax rule: forbid custom Webpack loader syntax in imports. (#​586, thanks @​fson!)
  • Add option newlines-between: "ignore" to order (#​519)
  • Added no-unassigned-import rule (#​529)
Breaking
Changed
  • imports-first is renamed to first. imports-first alias will continue to
    exist, but may be removed in a future major release.
  • Case-sensitivity: now specifically (and optionally) reported by no-unresolved.
    Other rules will ignore case-mismatches on paths on case-insensitive filesystems. (#​311)
Fixed

1.16.0 - 2016-09-22

Added
Fixed

1.15.0 - 2016-09-12

Added
Fixed

1.14.0 - 2016-08-22

Added
  • import/parsers setting: parse some dependencies (i.e. TypeScript!) with a different parser than the ESLint-configured parser. (#​503)
Fixed
  • namespace exception for get property from namespace import, which are re-export from commonjs module (#​499 fixes #​416, thanks @​wKich)

1.13.0 - 2016-08-11

Added
  • allowComputed option for namespace rule. If set to true, won't report
    computed member references to namespaces. (see #​456)
Changed
  • Modified no-nodejs-modules error message to include the module's name (#​453, #​461)
Fixed

1.12.0 - 2016-07-26

Added

1.11.1 - 2016-07-20

Fixed

1.11.0 - 2016-07-17

Added
Fixed
  • newline-after-import exception for multiple requires in an arrow
    function expression (e.g. () => require('a') || require('b')). (#​441, thanks @​ljharb)

1.10.3 - 2016-07-08

Fixed
  • removing Symbol dependencies (i.e. for-of loops) due to Node 0.10 polyfill
    issue (see #​415). Should not make any discernible semantic difference.

1.10.2 - 2016-07-04

Fixed
  • Something horrible happened during npm prepublish of 1.10.1.
    Several rm -rf node_modules && npm i and gulp clean && npm prepublishs later, it is rebuilt and republished as 1.10.2. Thanks @​rhettlivingston for noticing and reporting!

1.10.1 - 2016-07-02 [YANKED]

Added
  • Officially support ESLint 3.x. (peerDependencies updated to 2.x - 3.x)

1.10.0 - 2016-06-30

Added
Fixed
  • Fixed crash with newline-after-import related to the use of switch cases. (fixes #​386, thanks @​ljharb for reporting) (#​395)

1.9.2 - 2016-06-21

Fixed

1.9.1 - 2016-06-16

Fixed
  • Reordered precedence for loading resolvers. (#​373)

1.9.0 - 2016-06-10

Added
Fixed

1.8.1 - 2016-05-23

Fixed
  • export * from 'foo' now properly ignores a default export from foo, if any. (#​328/#​332, thanks @​jkimbo)
    This impacts all static analysis of imported names. (default, named, namespace, export)
  • Make order's newline-between option handle multiline import statements (#​313, thanks @​singles)
  • Make order's newline-between option handle not assigned import statements (#​313, thanks @​singles)
  • Make order's newline-between option ignore require statements inside object literals (#​313, thanks @​singles)
  • prefer-default-export properly handles deep destructuring, export * from ..., and files with no exports. (#​342+#​343, thanks @​scottnonnenberg)

1.8.0 - 2016-05-11

Added
Fixed

1.7.0 - 2016-05-06

Added
Fixed
  • extensions: fallback to source path for extension enforcement if imported
    module is not resolved. Also, never report for builtins (i.e. path). (#​296)

1.6.1 - 2016-04-28

Fixed
  • no-named-as-default-member: don't crash on rest props. (#​281, thanks @​SimenB)
  • support for Node 6: don't pass null to path functions.
    Thanks to @​strawbrary for bringing this up (#​272) and adding OSX support to the Travis
    config (#​288).

1.6.0 - 2016-04-25

Added
Changed
Fixed
  • named now properly ignores the source module if a name is re-exported from
    an ignored file (i.e. node_modules). Also improved the reported error. (thanks to @​jimbolla for reporting)
  • no-named-as-default-member had a crash on destructuring in loops (thanks for heads up from @​lemonmade)

1.5.0 - 2016-04-18

Added
Changed
  • Rearranged rule groups in README in preparation for more style guide rules
Removed
  • support for Node 0.10, via es6-* ponyfills. Using native Map/Set/Symbol.

1.4.0 - 2016-03-25

Added
  • Resolver plugin interface v2: more explicit response format that more clearly covers the found-but-core-module case, where there is no path.
    Still backwards-compatible with the original version of the resolver spec.
  • Resolver documentation
Changed
  • using package.json/files instead of .npmignore for package file inclusion (#​228, thanks @​mathieudutour)
  • using es6-* ponyfills instead of babel-runtime

1.3.0 - 2016-03-20

Major perf improvements. Between parsing only once and ignoring gigantic, non-module node_modules,
there is very little added time.

My test project takes 17s to lint completely, down from 55s, when using the
memoizing parser, and takes only 27s with naked babel-eslint (thus, reparsing local modules).

Added
  • This change log (#​216)
  • Experimental memoizing parser
Fixed
  • Huge reduction in execution time by only ignoring import/ignore setting if
    something that looks like an export is detected in the module content.

1.2.0 - 2016-03-19

Thanks @​lencioni for identifying a huge amount of rework in resolve and kicking
off a bunch of memoization.

I'm seeing 62% improvement over my normal test codebase when executing only
no-unresolved in isolation, and ~35% total reduction in lint time.

Changed

1.1.0 - 2016-03-15

Added
  • Added an ignore option to no-unresolved for those pesky files that no
    resolver can find. (still prefer enhancing the Webpack and Node resolvers to
    using it, though). See #​89 for details.

1.0.4 - 2016-03-11

Changed
Fixed
  • don't crash on self references (#​210)
  • correct cache behavior in eslint_d for deep namespaces (#​200)

1.0.3 - 2016-02-26

Changed
  • no-deprecated follows deep namespaces (#​191)
Fixed
  • namespace no longer flags modules with only a default export as having no
    names. (ns.default is valid ES6)

1.0.2 - 2016-02-26

Fixed
  • don't parse imports with no specifiers (#​192)

1.0.1 - 2016-02-25

Fixed
  • export stage-0 shared config
  • documented no-deprecated
  • deep namespaces are traversed regardless of how they get imported (#​189)

1.0.0 - 2016-02-24

Added
  • no-deprecated: WIP rule to let you know at lint time if you're using
    deprecated functions, constants, classes, or modules.
Changed
  • namespace: support deep namespaces (#​119 via #​157)

1.0.0-beta.0 - 2016-02-13

Changed
  • support for (only) ESLint 2.x
  • no longer needs/refers to import/parser or import/parse-options. Instead,
    ESLint provides the configured parser + options to the rules, and they use that
    to parse dependencies.
Removed
  • babylon as default import parser (see Breaking)

0.13.0 - 2016-02-08

Added
Removed
  • Removed vestigial no-require rule. no-commonjs is more complete.

0.12.2 - 2016-02-06 [YANKED]

Unpublished from npm and re-released as 0.13.0. See #​170.

0.12.1 - 2015-12-17

Changed
  • Broke docs for rules out into individual files.

0.12.0 - 2015-12-14

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.

0.11.0 - 2015-11-27

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

Earlier releases (0.10.1 and younger)

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



This PR has been generated by Renovate Bot.

@renovate renovate bot force-pushed the renovate/eslint-plugin-import-2.x branch 4 times, most recently from ab6cc20 to 21a61e0 Compare April 18, 2018 01:59
@renovate renovate bot force-pushed the renovate/eslint-plugin-import-2.x branch 2 times, most recently from d50b4d3 to 6bf6111 Compare April 29, 2018 06:09
@renovate renovate bot force-pushed the renovate/eslint-plugin-import-2.x branch from 6bf6111 to 22e3701 Compare April 29, 2018 06:09
@bokuweb bokuweb merged commit 47db610 into master May 1, 2018
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.

2 participants