All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning. This change log adheres to standards from Keep a CHANGELOG.
2.13.0 - 2018-06-24
- Add ESLint 5 support (#1122, thanks @ai and @ljharb)
- Add [
no-relative-parent-imports
] rule: disallow relative imports from parent directories (#1093, thanks @chrislloyd)
namespace
rule: ensure it works in eslint 5/ecmaVersion 2018 (thanks @ljharb)
2.12.0 - 2018-05-17
- Ignore type imports for
named
rule (#931, thanks @mattijsbliek) - Add documentation for
no-useless-path-segments
rule (#1068, thanks @manovotny) packageDir
option forno-extraneous-dependencies
can be array-valued (#1085, thanks @hulkish)
2.11.0 - 2018-04-09
- Fixer for
first
(#1046, thanks @fengkfengk) allow-require
option forno-commonjs
rule (#880, thanks @futpib)
- memory/CPU regression where ASTs were held in memory (#1058, thanks @klimashkin/@lukeapage)
2.10.0 - 2018-03-29
2.9.0 - 2018-02-21
- Add
group-exports
rule: style-guide rule to report use of multiple named exports (#721, thanks @robertrossmann) - Add
no-self-import
rule: forbids a module from importing itself. (#727, #449, #447, thanks @giodamelio). - Add
no-default-export
rule (#889, thanks @isiahmeadows) - Add
no-useless-path-segments
rule (#912, thanks @graingert and @danny-andrews) - ... and more! check the commits for v2.9.0
2.8.0 - 2017-10-18
exports-last
rule (#620 + #632, thanks @k15a)
- 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
no-absolute-path
picks up speed boost, optional AMD support (#843, thanks @jseminck)
2.6.1 - 2017-06-29
- update bundled node resolver dependency to latest version
2.6.0 - 2017-06-23
- update tests / peerDeps for ESLint 4.0 compatibility (#871, thanks @mastilver)
memo-parser
updated to requirefilePath
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.
2.4.0 - 2017-06-02 [YANKED]
Yanked due to critical issue in eslint-module-utils with cache key resulting from #839.
- Add
filePath
intoparserOptions
passed toparser
(#839, thanks @sompylasar) - Add
allow
option tono-unassigned-import
to allow for files that match the globs (#671, #737, thanks @kevin940726).
2.3.0 - 2017-05-18
no-anonymous-default-export
rule: report anonymous default exports (#712, thanks @duncanbeevers).- Add new value to
order
'snewlines-between
option to allow newlines inside import groups (#627, #628, thanks @giodamelio) - Add
count
option to thenewline-after-import
rule to allow configuration of number of newlines expected (#742, thanks @ntdb)
no-extraneous-dependencies
: useread-pkg-up
to simplify finding + loadingpackage.json
(#680, thanks @wtgtybhertgeghgtwtg)- Add support to specify the package.json
no-extraneous-dependencies
(#685, thanks @ramasilveyra)
- 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
- 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 animport
orexport
JS statementprefer-default-export
: fixed crash on export extensions (#653)
2.1.0 - 2016-11-02
- Add
no-named-default
rule: style-guide rule to report use of unnecessarily named default imports (#596, thanks @ntdb) no-extraneous-dependencies
: check globs against CWD + absolute path (#602 + #630, thanks @ljharb)
prefer-default-export
handles flowexport type
(#484 + #639, thanks @jakubsta)prefer-default-export
handles re-exported default exports (#609)- Fix crash when using
newline-after-import
with decorators (#592) - Properly report
newline-after-import
when next line is a decorator - Fixed documentation for the default values for the
order
rule (#601)
2.0.1 - 2016-10-06
- Fixed code that relied on removed dependencies. (#604)
2.0.0! - 2016-09-30
unambiguous
rule: report modules that are not unambiguously ES modules.recommended
shared config. Roughlyerrors
andwarnings
mixed together, with someparserOptions
in the mix. (#402)react
shared config: addedjsx: true
toparserOptions.ecmaFeatures
.- Added
no-webpack-loader-syntax
rule: forbid custom Webpack loader syntax in imports. (#586, thanks @fson!) - Add option
newlines-between: "ignore"
toorder
(#519) - Added
no-unassigned-import
rule (#529)
import/extensions
setting defaults to['.js']
. (#306)import/ignore
setting defaults to nothing, and ambiguous modules are ignored natively. This means importing from CommonJS modules will no longer be reported bydefault
,named
, ornamespace
, regardless ofimport/ignore
. (#270)newline-after-import
: Removed need for an empty line after an inlinerequire
call (#570)order
: Default value fornewlines-between
option is nowignore
(#519)
imports-first
is renamed tofirst
.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)
no-internal-modules
: support@
-scoped packages (#577+#578, thanks @spalger)
1.16.0 - 2016-09-22
- Added
no-dynamic-require
rule: forbidrequire()
calls with expressions. (#567, #568) - Added
no-internal-modules
rule: restrict deep package imports to specific folders. (#485, thanks @spalger!) extensions
: allow override of a chosen default with options object (#555, thanks @ljharb!)
no-named-as-default
no longer false-positives onexport default from '...'
(#566, thanks @preco21)default
: allow re-export of values from ignored files as default (#545, thanks @skyrpex)
1.15.0 - 2016-09-12
- Added an
allow
option tono-nodejs-modules
to allow exceptions (#452, #509). - Added
no-absolute-path
rule (#530, #538) max-dependencies
for specifying the maximum number of dependencies (bothimport
andrequire
) a module can have. (see #489, thanks @tizmagik)- Added glob option to config for
no-extraneous-dependencies
, after much bikeshedding. Thanks, @knpwrs! (#527)
no-named-as-default-member
Allow default import to have a property named "default" (#507, #508, thanks @jquense for both!)
1.14.0 - 2016-08-22
import/parsers
setting: parse some dependencies (i.e. TypeScript!) with a different parser than the ESLint-configured parser. (#503)
namespace
exception for get property fromnamespace
import, which are re-export from commonjs module (#499 fixes #416, thanks @wKich)
1.13.0 - 2016-08-11
allowComputed
option fornamespace
rule. If set totrue
, won't report computed member references to namespaces. (see #456)
- Modified
no-nodejs-modules
error message to include the module's name (#453, #461)
import/extensions
setting is respected in spite of the appearance of imports in an imported file. (fixes #478, thanks @rhys-vdw)
1.12.0 - 2016-07-26
import/external-module-folders
setting: a possibility to configure folders for "external" modules (#444, thanks @zloirock)
1.11.1 - 2016-07-20
newline-after-import
exception forswitch
branches withrequire
s iff parsed assourceType:'module'
. (still #441, thanks again @ljharb)
1.11.0 - 2016-07-17
- Added an
peerDependencies
option tono-extraneous-dependencies
to allow/forbid peer dependencies (#423, #428, thanks @jfmengels!).
newline-after-import
exception for multiplerequire
s in an arrow function expression (e.g.() => require('a') || require('b')
). (#441, thanks @ljharb)
1.10.3 - 2016-07-08
- 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
- Something horrible happened during
npm prepublish
of 1.10.1. Severalrm -rf node_modules && npm i
andgulp clean && npm prepublish
s later, it is rebuilt and republished as 1.10.2. Thanks @rhettlivingston for noticing and reporting!
1.10.1 - 2016-07-02 [YANKED]
- Officially support ESLint 3.x. (peerDependencies updated to
2.x - 3.x
)
1.10.0 - 2016-06-30
- Added new rule
no-restricted-paths
. (#155/#371, thanks @lo1tuma) import/core-modules
setting: allow configuration of additional module names, to be treated as builtin modules (a lapath
, etc. in Node). (#275 + #365, thanks @sindresorhus for driving)- React Native shared config (based on comment from #283)
- 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
- Issues with ignored/CJS files in
export
andno-deprecated
rules. (#348, #370)
1.9.1 - 2016-06-16
- Reordered precedence for loading resolvers. (#373)
1.9.0 - 2016-06-10
- Added support TomDoc comments to
no-deprecated
. (#321, thanks @josh) - Added support for loading custom resolvers (#314, thanks @le0nik)
prefer-default-export
handlesexport function
andexport const
in same file (#359, thanks @scottnonnenberg)
1.8.1 - 2016-05-23
export * from 'foo'
now properly ignores adefault
export fromfoo
, if any. (#328/#332, thanks @jkimbo) This impacts all static analysis of imported names. (default
,named
,namespace
,export
)- Make
order
'snewline-between
option handle multiline import statements (#313, thanks @singles) - Make
order
'snewline-between
option handle not assigned import statements (#313, thanks @singles) - Make
order
'snewline-between
option ignorerequire
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
prefer-default-export
, new rule. (#308, thanks @gavriguy)
- Ignore namespace / ES7 re-exports in
no-mutable-exports
. (#317, fixed by #322. thanks @borisyankov + @jfmengels) - Make
no-extraneous-dependencies
handle scoped packages (#316, thanks @jfmengels)
1.7.0 - 2016-05-06
newline-after-import
, new rule. (#245, thanks @singles)- Added an
optionalDependencies
option tono-extraneous-dependencies
to allow/forbid optional dependencies (#266, thanks @jfmengels). - Added
newlines-between
option toorder
rule (#298, thanks @singles) - add
no-mutable-exports
rule (#290, thanks @josh) import/extensions
setting: a list of file extensions to parse as modules and search forexport
s. If unspecified, all extensions are considered valid (for now). In v2, this will likely default to['.js', MODULE_EXT]
. (#297, to fix #267)
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
no-named-as-default-member
: don't crash on rest props. (#281, thanks @SimenB)- support for Node 6: don't pass
null
topath
functions. Thanks to @strawbrary for bringing this up (#272) and adding OSX support to the Travis config (#288).
1.6.0 - 2016-04-25
- add
no-named-as-default-member
towarnings
canned config - add
no-extraneous-dependencies
rule (#241, thanks @jfmengels) - add
extensions
rule (#250, thanks @lo1tuma) - add
no-nodejs-modules
rule (#261, thanks @jfmengels) - add
order
rule (#247, thanks @jfmengels) - consider
resolve.fallback
config option in the webpack resolver (#254)
imports-first
now allows directives (i.e.'use strict'
) strictly before any imports (#256, thanks @lemonmade)
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
- report resolver errors at the top of the linted file
- add
no-namespace
rule (#239, thanks @singles) - add
no-named-as-default-member
rule (#243, thanks @dmnd)
- Rearranged rule groups in README in preparation for more style guide rules
- support for Node 0.10, via
es6-*
ponyfills. Using native Map/Set/Symbol.
1.4.0 - 2016-03-25
- 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
- using
package.json/files
instead of.npmignore
for package file inclusion (#228, thanks @mathieudutour) - using
es6-*
ponyfills instead ofbabel-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).
- Huge reduction in execution time by only ignoring
import/ignore
setting if something that looks like anexport
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.
- added caching to core/resolve via #214, configured via
import/cache
setting
1.1.0 - 2016-03-15
- Added an
ignore
option tono-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
- respect hoisting for deep namespaces (
namespace
/no-deprecated
) (#211)
1.0.3 - 2016-02-26
- no-deprecated follows deep namespaces (#191)
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
- don't parse imports with no specifiers (#192)
1.0.1 - 2016-02-25
- 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
no-deprecated
: WIP rule to let you know at lint time if you're using deprecated functions, constants, classes, or modules.
1.0.0-beta.0 - 2016-02-13
- support for (only) ESLint 2.x
- no longer needs/refers to
import/parser
orimport/parse-options
. Instead, ESLint provides the configured parser + options to the rules, and they use that to parse dependencies.
babylon
as default import parser (see Breaking)
0.13.0 - 2016-02-08
no-commonjs
ruleno-amd
rule
- 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
- Broke docs for rules out into individual files.
0.12.0 - 2015-12-14
- Ignore
import/ignore
setting if exports are actually found in the parsed module. Does this to support use ofjsnext:main
innode_modules
without the pain of managing an allow list or a nuanced deny list.
0.11.0 - 2015-11-27
- Resolver plugins. Now the linter can read Webpack config, properly follow aliases and ignore externals, dismisses inline loaders, etc. etc.!
See GitHub release notes for info on changes for earlier releases.