patch namespaces

bugfixes:

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

one-oh, f'real

• 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. 😅

one-oh!

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. 😅

Webpack resolver: nested aliases

#166: allow aliases to contain separators. (thanks @nosnickid!)

no-old-and-busted

no-commonjs and no-amd rules added. (thanks @xjamundx for donating code to get these going)

semver-fail

Unpublished and re-released as 0.13.0. See #170.

docs

Moved rule details into separate files, so the README is shorter and does not distract from config settings (resolvers, import/parser, etc.).

No code changes, should be functionally identical to v0.12.0.

ignores on ignores

• Ignore import/ignore 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 a whitelist or a nuanced blacklist. May be removed pending how surprising/helpful it ends up being.

webpack resolver: v0.1.4

• support for absolute config paths (thanks @nosnickid! via #136)
• support for eslint-loader, by resolving relative paths. (thanks @xjamundx! via #138)
• support for array resolve.root, where TIL bower_components should live (not in moduleDirectories)

custom resolvers!

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