Fix: max-len rule overestimates the width of some tabs (fixes #4661)
max-len incorrectly assumed that all tab characters were the same width
as the tab stops.
Merge pull request #4647 from gkz/issue4507
Fix: Use oneValuePerFlag for --ignore-pattern option (fixes #4507)
Fix: Use oneValuePerFlag for --ignore-pattern option (fixes #4507)
Updates optionator from 0.6.0 to 0.7.1
Multiple ignore patterns must be specified by using the flag multiple
times, not by using a comma (since the pattern could include a comma)
Merge pull request #4644 from betaorbust/issue4642
Upgrade: Handlebars to >= 4.0.5 for security reasons (fixes #4642)
Upgrade: Handlebars to >= 4.0.5 for security reasons (fixes #4642)
NSP has a reported security vulnerability with old versions of uglify, which is used by handlebars < 4.0.5.
https://nodesecurity.io/advisories/48
This update changes eslint's minimum handlebars version up from 4.0.0 to 4.0.5.
Merge pull request #4639 from eslint/issue4372
Update: Add class body support to indent rule (fixes #4372)
Update: Add class body support to indent rule (fixes #4372)
Merge pull request #4597 from mysticatea/no-use-before-define/noclass
Update: add class option to no-use-before-define
Merge pull request #4617 from kaicataldo/fixes4605
Update: Add 'method' option to no-empty (fixes #4605)
Merge pull request #4624 from eslint/issue-4451
Breaking: Treat package.json like the rest of configs (fixes #4451)
Breaking: Treat package.json like the rest of configs (fixes #4451)
Merge pull request #4574 from kaicataldo/objectshorthandignoreconstructors
Update: Add option to ignore constructor functions in object-shorthand rule (fixes #4487)
Merge pull request #4547 from platinumazure/ignore-pattern-array-tests
Fix: Adding options unit tests for --ignore-pattern (refs #4507)
Merge pull request #4614 from eslint/issue-4578
Breaking: Remove autofix from eqeqeq (fixes #4578)
Merge pull request #4629 from molee1905/master
Docs: writing mistake
Docs: writing mistake
Merge pull request #4621 from eslint/issue4085
Breaking: Remove ES6 global variables from builtins (fixes #4085)
Update: Add 'method' option to no-empty (fixes #4605)
Breaking: Remove autofix from eqeqeq (fixes #4578)
Merge pull request #4253 from mysticatea/no-unreachable/code-path-analysis
Fix: no-unreachable with the code path
Merge pull request #4252 from mysticatea/no-this-before-super/code-path-analysis
Fix: no-this-before-super with the code path analysis
Merge pull request #4251 from mysticatea/no-fallthrough/code-path-analysis
Fix: no-fallthrough with the code path analysis
Merge pull request #4249 from mysticatea/constructor-super/code-path-analysis
Fix: constructor-super with the code path analysis
Merge pull request #4612 from eslint/issue4229
Fix: Handle forbidden LineTerminators in no-extra-parens (fixes #4229)
Breaking: Remove ES6 global variables from builtins (fixes #4085)
This upgrades to globals@8.14.0, which has separate es5 and es6
environments. Only ES5 global variables are considered builtin now, and
ES6 global variables are supplied as part of the es6 environment.
Fix: Handle forbidden LineTerminators in no-extra-parens (fixes #4229)
Previously, this rule would warn about excess parentheses even when they
were syntactically significant and removing them would alter the meaning
of a program. There are three applicable productions in the grammar with
the restriction [no LineTerminator here]:
ReturnStatement[Yield]: return [no LineTerminator here] Expression; return [no LineTerminator here] Expression[In, ?Yield]; ThrowStatement[Yield]: throw [no LineTerminator here] Expression[In, ?Yield]; YieldExpression[In]: yield [no LineTerminator here] * AssignmentExpression[?In, Yield] yield [no LineTerminator here] AssignmentExpression[?In, Yield]
If the expression following a return, throw, or yield is on a new
line, it must be wrapped in parentheses, and this rule should not warn.
It should, however, still check for double parentheses, since the second
set would be unnecessary.
Thanks to @michaelficarra for pasting the relevant portions of the spec.
Update: Option to ignore constructor Fns object-shorthand (fixes #4487)
Merge pull request #4610 from SpainTrain/dont-module-cache-package-json
Do not implicitly cache package.json
Merge pull request #4609 from eslint/issue4608
Fix: Check YieldExpression argument in no-extra-parens (fixes #4608)
Fix: Check YieldExpression argument in no-extra-parens (fixes #4608)
2.0.0-alpha-1 / 2015-12-11
array-callback-return
ruleno-use-before-define
checks invalid initializerno-use-before-define
checks invalid initializer (fixes #4280)array-callback-return
rule (fixes #1128)indent
rule (fixes #4372)indent
rule (fixes #4372)no-use-before-define
no-unreachable
with the code pathno-this-before-super
with the code path analysisno-fallthrough
with the code path analysisconstructor-super
with the code path analysisglobals@8.14.0
, which has separatees5
andes6
environments. Only ES5 global variables are considered builtin now, and ES6 global variables are supplied as part of thees6
environment.[no LineTerminator here]
:ReturnStatement[Yield]: return [no LineTerminator here] Expression; return [no LineTerminator here] Expression[In, ?Yield]; ThrowStatement[Yield]: throw [no LineTerminator here] Expression[In, ?Yield]; YieldExpression[In]: yield [no LineTerminator here] * AssignmentExpression[?In, Yield] yield [no LineTerminator here] AssignmentExpression[?In, Yield]
If the expression following areturn
,throw
, oryield
is on a new line, it must be wrapped in parentheses, and this rule should not warn. It should, however, still check for double parentheses, since the second set would be unnecessary. Thanks to @michaelficarra for pasting the relevant portions of the spec.package.json
package.json
(fixes #4611)package.json
on every config load by not usingrequire
consistent-return
comes to checking the last path.consistent-return
checks the last (refs #3530, fixes #3373)no-use-before-define
(fixes #3944)no-undef
no-unreachable
with the code path (refs #3530, fixes #3939)no-this-before-super
with the code path analysis (refs #3530)no-fallthrough
with the code path analysis (refs #3530)constructor-super
with the code path analysis (refs #3530)prefer-rest-params
rulethis
prefer-const
begins to cover separating initno-eval
come to catch indirect eval1.10.3 / 2015-12-01
curly
rule (fixes #4571)