Eslint Plugin Import: v1.0.0 Release

Release date:
February 24, 2016
Previous version:
v1.0.0-beta.0 (released February 24, 2016)
Magnitude:
1,591 Diff Delta
Contributors:
2 total committers
Data confidence:
Commits:

24 Commits in this Release

Ordered by the degree to which they evolved the repo in this version.

Authored January 21, 2016
Authored February 24, 2016
Authored February 22, 2016
Authored February 22, 2016
Authored February 23, 2016
Authored January 26, 2016
Authored February 6, 2016
Authored February 22, 2016
Authored February 22, 2016
Authored February 22, 2016
Authored February 23, 2016
Authored February 22, 2016
Authored February 6, 2016
Authored January 26, 2016
Authored February 24, 2016

Top Contributors in v1.0.0

ben-mosher-7b5f
greenkeeper[bot]

Directory Browser for v1.0.0

We haven't yet finished calculating and confirming the files and directories changed in this release. Please check back soon.

Release Notes Published

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

From the beta 1.0 release notes:

Update, verified to work with ESLint 2.0.

"Breaking" changes from 0.13.0:

no longer needs/refers to import/parser or import/parse-options. instead, ESLint provided the configured parser + options to the rules, and they use that to parse dependencies.

Shouldn't hurt to leave it there, and I suspect 99.999% of installs have import/parser === parser.

This also means the plugin uses espree instead of babylon if no parser is configured. Wouldn't expect this to hurt in general, but it is a potentially breaking difference.

eslint-config-import is no longer supported. Instead, use the shared configs directly exported by the plugin. See the README for details.

Nothing groundbreaking, but import/parser has been a thorny issue for the whole life of the plugin, and I'm glad to finally be rid of it. :sweat_smile: