one-oh!
Update, verified to work with ESLint 2.0.
"Breaking" changes from 0.13.0:
-
no longer needs/refers to
import/parser
orimport/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 ofbabylon
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. 😅