ESLint - Pluggable JavaScript linter

ESLint v2.11.1 released

Mon, 30 May 2016 00:00:00 +0000

ESLint v2.11.1 released

We just pushed ESLint v2.11.1, which is a patch release upgrade of ESLint. This release fixes several bugs found in the previous release.

Bug Fixes

03beb27 Fix: no-useless-rename false positives (fixes #6266) (#6267) (alberto)
113c1a8 Fix: max-statements-per-line false positive at exports (fixes #6264) (#6268) (Toru Nagashima)
64b0d0c Fix: failed to parse /*eslint comments by colon (fixes #6224) (#6258) (Toru Nagashima)

c8936eb Build: Don’t check commit count (fixes #5935) (#6263) (Nicholas C. Zakas)

Documentation

fe89037 Docs: Fix rule name in example (#6279) (Kenneth Williams)

ESLint v2.11.0 released

Fri, 27 May 2016 00:00:00 +0000

ESLint v2.11.0 released

We just pushed ESLint v2.11.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.

Highlights

This is a summary of the major changes you need to know about for this version of ESLint.

JSCS Compatibility

We’ve started our JSCS compatibility work by continuing to add new rules and rule options to fill in the gaps between what ESLint can do and what JSCS can do. This release includes the new no-useless-rename rule, which corresponds to the JSCS disallowIdenticalDestructuringNames.

You can follow our progress on JSCS compatibility by looking at the milestone.

New Rules

The new rules included in this release are:

Features

fea8fe6 New: no-useless-rename (fixes #6058) (#6249) (Kai Cataldo)
088bda9 New: unicode-bom rule to allow or disallow BOM (fixes #5502) (#6230) (Andrew Johnston)
04bd586 New: Disallow use of Object.prototype methods on objects (fixes #2693) (#6107) (Andrew Levine)

Enhancements

74c458d Update: key-spacing rule whitespace fixer (fixes #6167) (#6169) (Ruurd Moelker)
53754ec Update: max in max-statements-per-line should be >=0 (fixes #6171) (#6172) (alberto)
54d1201 Update: Add treatUndefinedAsUnspecified option (fixes #6026) (#6194) (Kenneth Williams)
18152dd Update: Add checkLoops option to no-constant-condition (fixes #5477) (#6202) (Kai Cataldo)

Bug Fixes

77dd2b4 Fix: On –init, print message when package.json is invalid (fixes #6257) (#6261) (Kai Cataldo)
7f60186 Fix: --ignore-pattern can’t uningnore files (fixes #6127) (#6253) (alberto)
b4cff9d Fix: Incorrect object-property-newline behavior (fixes #6207) (#6213) (Rafał Ruciński)
ee0cd58 Fix: newline-before-return shouldn’t disallow newlines (fixes #6176) (#6217) (alberto)
d4f5526 Fix: vars-on-top crashs at export declarations (fixes #6210) (#6220) (Toru Nagashima)
14bfc03 Fix: comma-dangle wrong autofix (fixes #6233) (#6235) (Toru Nagashima)
c10c07f Fix: lost code in autofixing (refs #6233) (#6234) (Toru Nagashima)
7644908 Fix: no-multiple-empty-lines BOF and EOF defaults (fixes #6179) (#6180) (Ruurd Moelker)
72335eb Fix: max-statements-per-line false positive (fixes #6173, fixes #6153) (#6192) (Toru Nagashima)
9fce04e Fix: generator-star-spacing false positive (fixes #6135) (#6168) (Toru Nagashima)

Documentation

35b4656 Docs: Edit arrow-parens.md to show correct output value (#6245) (Adam Terlson)
cdd65d7 Docs: added examples for arrow-body-style (refs #5498) (#6242) (Tieme van Veen)
e6d5b1f Docs: Add rule deprecation section to user guide (fixes #5845) (#6201) (Kai Cataldo)

Dependency Upgrades

777941e Upgrade: doctrine to 1.2.2 (fixes #6121) (#6231) (alberto)

ESLint v2.10.2 released

Mon, 16 May 2016 00:00:00 +0000

ESLint v2.10.2 released

We just pushed ESLint v2.10.2, which is a patch release upgrade of ESLint. This release fixes several bugs found in the previous release.

Bug Fixes

bda5de5 Fix: Remove default parser from CLIEngine options (fixes #6182) (#6183) (alberto)

Documentation

e59e5a0 Docs: Describe options in rules under Possible Errors part 3 (#6105) (Mark Pedrotti)

842ab2e Build: Run phantomjs tests using karma (fixes #6128) (#6178) (alberto)

ESLint v2.10.1 released

Sat, 14 May 2016 00:00:00 +0000

ESLint v2.10.1 released

We just pushed ESLint v2.10.1, which is a patch release upgrade of ESLint. This release fixes several bugs found in the previous release.

Highlights

This release fixes an issue when using parser other than default one. And a few other minor issue found after the last release.

Bug Fixes

9397135 Fix: valid-jsdoc false positive at default parameters (fixes #6097) (#6170) (Toru Nagashima)
2166ad4 Fix: warning & error count in CLIEngine.getErrorResults (fixes #6155) (#6157) (alberto)
1e0a652 Fix: ignore empty statements in max-statements-per-line (fixes #6153) (#6156) (alberto)
f9ca0d6 Fix: no-extra-parens to check for nulls (fixes #6161) (#6164) (Gyandeep Singh)
d095ee3 Fix: Parser merge sequence in config (fixes #6158) (#6160) (Gyandeep Singh)
f33e49f Fix: no-return-assign to check for null tokens (fixes #6159) (#6162) (Gyandeep Singh)

ESLint v2.10.0 released

Fri, 13 May 2016 00:00:00 +0000

ESLint v2.10.0 released

We just pushed ESLint v2.10.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.

Highlights

This is a summary of the major changes you need to know about for this version of ESLint.

New Rules

This version introduces one new rule:

object-property-newline

New Rule Options

A few rules got additional options:

Features

f84eb80 New: Add new rule object-property-newline (fixes #5667) (#5933) (Vitor Balocco)

Enhancements

767da6f Update: add returnAssign option to no-extra-parens (fixes #6036) (#6095) (Kai Cataldo)
0734967 Update: Add an option to prefer-const (fixes #5692) (#6040) (Toru Nagashima)
7941d5e Update: Add autofix for lines-around-comment (fixes #5956) (#6062) (alberto)
8633e4d Update: multipass should not exit prematurely (fixes #5995) (#6048) (alberto)
3c44c2c Update: Adds an avoidQuotes option for object-shorthand (fixes #3366) (#5870) (Chris Sauvé)
a3a6e06 Update: no-irregal-whitespace in a regular expression (fixes #5840) (#6018) (Linda_pp)

Bug Fixes

10b0933 Fix: Optimize no-irregular-whitespace for the common case (fixes #6116) (#6117) (Andres Suarez)
e13e696 Fix: _ and $ in isES5Constructor (fixes #6085) (#6094) (Kevin Locke)
67916b9 Fix: no-loop-func crashed (fixes #6130) (#6138) (Toru Nagashima)
d311a62 Fix: Sort fixes consistently even if they overlap (fixes #6124) (#6133) (alberto)
067db14 Fix: Replace assert.deepEqual by lodash.isEqual (fixes #6111) (#6112) (alberto)
52fdf04 Fix: no-multiple-empty-lines duplicate errors at BOF (fixes #6113) (#6114) (alberto)
ef739cd Fix: Merge various command line configs at the same time (fixes #6104) (#6108) (Ed Lee)
6df4b23 Fix: no-return-assign warning nested expressions (fixes #5913) (#6041) (Toru Nagashima)
d40017f Fix: comma-style accounts for parens in array (fixes #6006) (#6038) (Kai Cataldo)
a9a4652 Fix: throw when rule uses fix but meta.fixable not set (fixes #5970) (#6043) (Vitor Balocco)
388d6f8 Fix: no-sequences false negative at arrow expressions (fixes #6082) (#6083) (Toru Nagashima)
a66bf19 Fix: lines-around-comment multiple errors on same line (fixes #5965) (#5994) (alberto)
ef8cbff Fix: object-shorthand should only lint computed methods (fixes #6015) (#6024) (Kai Cataldo)
dd8bf93 Fix: blockless else in max-statements-per-line (fixes #5926) (#5993) (Glen Mailer)
3db2e89 Fix: Do not swallow exceptions in CLIEngine.getFormatter (fixes #5977) (#5978) (Gustav Nikolaj)
eb2fb44 Fix: Always ignore defaults unless explicitly passed (fixes #5547) (#5820) (Ian VanSchooten)
2f15354 Fix: Removed false positives of break and continue (fixes #5972) (#6000) (Onur Temizkan)

Documentation

098cd9c Docs: Distinguish examples in rules under Stylistic Issues part 4 (#6136) (Kenneth Williams)
805742c Docs: Clarify JSX option usage (#6132) (Richard Collins)
36bec90 Docs: linkify URLs in development-environment.md (#6150) (chrisjshull)
29c401a Docs: Convert rules in index under Removed from list to table (#6091) (Mark Pedrotti)
6294459 Docs: Correct syntax for default ignores and .eslintignore example (#6118) (alberto)
e6f56da Docs: Document --ignore-pattern (#6120) (alberto)
c4fc39b Docs: Update headings of rules under Removed (refs #5774) (#6102) (Mark Pedrotti)
04563ca Docs: Describe options in rules under Possible Errors part 2 (#6063) (Mark Pedrotti)
0b67170 Docs: Correct default for one-var-declaration-per-line (fixes #6017) (#6022) (Ed Lee)
992d9cf Docs: Fix typography/teriminology in indent doc (fixes #6045) (#6044) (Rich Trott)
ad10106 Docs: Update comma-style docs (#6039) (Kai Cataldo)
8e96064 Docs: Clarify rule example in README since we allow string error levels (#6061) (Kevin Partington)
a2cc54e Docs: Organize meta and describe visitor in Working with Rules (#5967) (Mark Pedrotti)
d5f4104 Docs: mention parsing errors in strict mode (fixes #5485) (#5991) (Mark Pedrotti)
249732e Docs: Move docs from eslint.github.io (fixes #5964) (#6012) (Nicholas C. Zakas)
4c2de6c Docs: Add example of diff clarity to comma-dangle rule docs (#6035) (Vitor Balocco)
ab57e94 Docs: Add example of diff clarity to newline-per-chained-call (#5986) (Vitor Balocco)
88bc014 Docs: Update readme info about jshint (#6027) (alberto)
a2c15cc Docs: put config example in code block (#6005) (Amos Wenger)
a5011cb Docs: Fix a wrong examples’ header of prefer-arrow-callback. (#6020) (Toru Nagashima)
1484ede Docs: Typo in nodejs-api (#6025) (alberto)
ade6a9b Docs: typo: “eslint-disable-line” not “eslint disable-line” (#6019) (Will Day)

06f6252 Build: Use split instead of slice/indexOf for commit check (fixes #6109) (#6110) (Ed Lee)
716345f Build: Match rule id at beginning of heading (refs #5774) (#6089) (Mark Pedrotti)
dc538aa Build: Pin proxyquire to “>=1.0.0 <1.7.5” (fixes #6096) (#6100) (alberto)

Chores

5d390b2 Chore: Replace deprecated calls to context - batch 4 (fixes #6029) (#6087) (alberto)
4ae39d2 Chore: Replace deprecated calls to context - batch 3 (refs #6029) (#6056) (alberto)
cd1b057 Chore: Replace deprecated calls to context - batch 2 (refs #6029) (#6049) (alberto)
9b9d76c Chore: Replace deprecated calls to context - batch 1 (refs #6029) (#6034) (alberto)

ESLint v2.9.0 released

Fri, 29 Apr 2016 00:00:00 +0000

ESLint v2.9.0 released

We just pushed ESLint v2.9.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.

Highlights

This is a summary of the major changes you need to know about for this version of ESLint.

Improved Autofix

This release features a new version of autofix. Now, when you use the --fix option, ESLint will make multiple passes over your code in an attempt to fix as many issues as possible. As a result, autofix will take more time now than it did previously, but we believe that this change will ultimately result in less developer time spent fixing things that can be automatically fixed by ESLint.

Additionally, due to implementing multipass autofix, we were able to extend autofix to more rules. The following rules now will be autofixed:

New Rules

This version introduces some new rules:

Features

e606523 New: Rule no-unsafe-finally (fixes #5808) (#5932) (Onur Temizkan)
a01b412 New: Add no-useless-computed-key rule (fixes #5402) (Burak Yigit Kaya)

Enhancements

e2ad1ec Update: object-shorthand lints computed methods (fixes #5871) (#5963) (Chris Sauvé)
51ddd4b Update: Use process @abstract when processing @return (fixes #5941) (#5945) (Simon Schick)
52a4bea Update: Add autofix for no-whitespace-before-property (fixes #5927) (#5951) (alberto)
586478e Update: Add autofix for comma-dangle (fixes #3805) (#5925) (alberto)
cb78585 Update: Add allowUnboundThis to prefer-arrow-callback (fixes #4668) (Burak Yigit Kaya)
19f6fff Update: Autofixing does multiple passes (refs #5329) (Nicholas C. Zakas)
2b39461 Update: commentPattern option for default-case rule (fixes #5803) (Artyom Lvov)

Bug Fixes

a8a2cd8 Fix: Avoid autoconfig crashes from inline comments (fixes #5992) (#5999) (Ian VanSchooten)
141b778 Fix: no-control-regex literal handling fixed. (fixes #5737) (#5943) (Efe Gürkan YALAMAN)
577757d Fix: Clarify color option (fixes #5928) (#5974) (Grant Snodgrass)
1e7a3ef Fix: id-match false positive in property values (fixes #5885) (#5960) (Mike Sherov)
f842d18 Fix: no-this-before-super crash on unreachable paths (fixes #5894) (Toru Nagashima)
f1b2992 Fix: no-useless-escape false positive in JSXAttribute (fixes #5882) (Toru Nagashima)
a9c5323 Fix: Install ESLint on init if not installed (fixes #5833) (Kai Cataldo)

Documentation

e7e6581 Docs: Update CLA link (#5980) (Gustav Nikolaj)
46e058d Docs: Correct typo in configuring.md (#5957) (Nick S. Plekhanov)
43f6d05 Docs: Update docs to refer to column (#5937) (Sashko Stubailo)
a4f9c5a Docs: Distinguish examples in rules under Stylistic Issues part 3 (Kenneth Williams)
249eb40 Docs: Clarify init sets up local installation (fixes #5874) (Kai Cataldo)
6cd8c86 Docs: Describe options in rules under Possible Errors part 1 (Mark Pedrotti)
a02960b Docs: Fix missing delimiter in README links (Kevin Partington)
3a9e72c Docs: Update developer guide with new standards (Nicholas C. Zakas)
74674ad Docs: Move sort-imports to ‘ECMAScript 6’ (Kenneth Williams)
ae69ddb Docs: Fix severity type in example (Kenneth Williams)
1e4b0ca Docs: Reduce length of paragraphs in rules index (Mark Pedrotti)
8cfe1eb Docs: Fix a wrong option (Zach Orlovsky)
8f6739f Docs: Add alberto as reviewer (alberto)
2ae4938 Docs: Fix message for inline-config option (alberto)
089900b Docs: Fix a wrong rule name in an example (Toru Nagashima)
c032b41 Docs: Fix emphasis (Toru Nagashima)
ae606f0 Docs: Update JSCS info in README (alberto)
ed38358 Docs: Removed incorrect example (James M. Greene)
af3113c Docs: Fix config comments in indent docs (Brandon Mills)

Dependency Upgrades

23b00e0 Upgrade: npm-license to 0.3.2 (fixes #5996) (#5998) (alberto)
377167d Upgrade: ignore to 3.1.2 (fixes #5979) (#5988) (alberto)
25d626a Upgrade: espree 3.1.4 (fixes #5923, fixes #5756) (Kai Cataldo)

0be26bc Build: Add nodejs 6 to travis (fixes #5971) (#5973) (Gyandeep Singh)
0023fe6 Build: Add “chore” to commit tags (fixes #5880) (#5929) (Mike Sherov)

Chores

42d1ecc Chore: Add metadata to existing rules - Batch 7 (refs #5417) (#5969) (Vitor Balocco)
d24516a Chore: Add metadata to existing rules - Batch 6 (refs #5417) (#5966) (Vitor Balocco)
5f8abab Chore: Add metadata to existing rules - Batch 5 (refs #5417) (#5944) (Vitor Balocco)
0562f77 Chore: Add missing newlines to test cases (fixes #5947) (Rich Trott)
fc78e78 Chore: Enable quote-props rule in eslint-config-eslint (refs #5188) (#5938) (Gyandeep Singh)
e7c0737 Chore: Enable no-console rule in eslint-config-eslint (refs #5188) (Kevin Partington)
9afb9cb Chore: Remove workaround for espree and escope bugs (fixes #5852) (alberto)
3ffc582 Chore: Update copyright and license info (alberto)
02be29f Chore: Remove CLA check from bot (Nicholas C. Zakas)
220713e Chore: Add metadata to existing rules - Batch 4 (refs #5417) (Vitor Balocco)
df53414 Chore: Include jQuery Foundation info (Nicholas C. Zakas)

ESLint Joins The jQuery Foundation

Tue, 19 Apr 2016 00:00:00 +0000

ESLint Joins the jQuery Foundation

I’ve believed for a while that once an open source project reaches a certain level of ubiquity, the maintainers have a responsibility to ensure its survival for the good of the community. Over the past couple of years, I watched as important projects hit roadblocks: YUI abruptly shut down, Node.js splintered before merging back together, and Express was left in a state of disarray. Communities were left scrambling, unsure what to rely on. During this time, I started formulating a plan for how to keep ESLint from falling into the same pattern.

Today, ESLint joins the jQuery Foundation to ensure that the project will live on for as long as the community needs it. The jQuery Foundation has been a great home for projects like jQuery and Esprima, and after merging with the Dojo Foundation, is also the home of projects such as Lodash and Grunt. I’m proud to have ESLint listed alongside some of the most important and influential projects in the JavaScript ecosystem.

From my perspective, ESLint joining the jQuery Foundation ensures a few things:

The project will go on even after I’ve left it. While I don’t have any plans to leave the project, history shows that it’s quite common for the creators of open source projects to eventually leave. From John Resig leaving jQuery to Ryan Dahl leaving Node.js, I can’t picture myself being immune from the same path.
ESLint will never be “sold” to a company. As the events with Node.js and Express show, this type of relationship doesn’t always work out smoothly. I feel that the ESLint community deserves this type of guarantee so there’s no question about whether or not it’s safe to rely on ESLint.
The ESLint project will be up-to-date with all the latest best practices and legal advice relevant to open source.

It’s my hope that these assurances will help the ESLint community to continue to grow and thrive.

What Is Changing

While the transition to the jQuery Foundation is mostly transparent, there are a few things that are changing:

CLA - ESLint will change from using its own CLA to the jQuery Foundation CLA. If you previously signed the ESLint CLA, we’ll be asking you to sign the jQuery Foundation CLA the next time you submit a pull request.
Code of Conduct - ESLint will change to use the jQuery Foundation Code of Conduct instead of our own. This change is minimal because we used the jQuery Foundation’s Code of Conduct as the model for own. The only real change here is that the Foundation will be overseeing the Code of Conduct and handling violations directly instead of being handled by the ESLint team.
Legal - The jQuery Foundation will be handling all legal aspects of ESLint going forward. That means they are the copyright holders and will also be registering ESLint and the ESLint logo as trademarks to protect the project.

What Isn’t Changing

Everything else will be the same as it always has been. Specifically:

We will continue to use the ESLint GitHub organization for all ESLint-related projects.
The ESLint team will continue to maintain and develop ESLint going forward.
All ESLint team members will continue to be team members.

A New Beginning

I hope you’re as excited about ESLint joining the jQuery Foundation as I am. I see this as an important step in the life of ESLint as a whole. The ESLint community has made the project the success that it is, and moving ESLint into the jQuery Foundation is my way of saying that the project is, and always will be, for the community.

– Nicholas

ESLint v2.8.0 released

Fri, 15 Apr 2016 00:00:00 +0000

ESLint v2.8.0 released

We just pushed ESLint v2.8.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.

Enhancements

76913b6 Update: Add metadata to existing rules - Batch 3 (refs #5417) (Vitor Balocco)
fb3c2eb Update: allow template literals (fixes #5234) (Jonathan Haines)
5a4a935 Update: Add metadata to existing rules - Batch 2 (refs #5417) (Vitor Balocco)
f8db9c9 Update: add nestedBinaryExpressions to no-extra-parens (fixes #3065) (Ilya Volodin)
0045d57 Update: allowNamedFunctions in prefer-arrow-callback (fixes #5675) (alberto)
19da72a Update: Add metadata to existing rules - Batch 1 (refs #5417) (Vitor Balocco)
24b6215 Update: Include ‘typeof’ in rule ‘no-constant-condition’ (fixes #5228) (Vamshi krishna)
6fd7d82 Update: Change order in eslint --init env options (fixes #5742) (alberto)
6703c02 Update: no-useless-escape / exact locations of errors (fixes #5751) (Onur Temizkan)
b0e6bc4 Update: add allowEmptyCatch option to no-empty (fixes #5800) (Kai Cataldo)
228f201 Update: commentPattern option for no-fallthrough rule (fixes #5757) (Artyom Lvov)
2b202fc Update: Add ignore option to space-before-function-parens (fixes #4127) (Craig Silverstein)

Bug Fixes

34ad8d2 Fix: Check that module.paths exists (fixes #5791) (Nicholas C. Zakas)
ea2e625 Fix: newline-before-return handles return as first token (fixes #5816) (Kevin Partington)
cc14e43 Fix: no-fallthrough empty case with comment (fixes #5799) (alberto)
13c8b14 Fix: LogicalExpression checks for short circuit (fixes #5693) (Vamshi krishna)
73b225e Fix: Document and fix metadata (refs #5417) (Ilya Volodin)
c59d909 Fix: Extra paren check around object arrow bodies (fixes #5789) (Brandon Mills)
02743d5 Fix: catch self-assignment operators in no-magic-number (fixes #4400) (alberto)
ccd8ca9 Fix: Added property onlyDeclaration to id-match rule (fixes #3488) (Gajus Kuizinas)
3d84b91 Fix: ignore trailing whitespace in template literal (fixes #5786) (Kai Cataldo)
24c12ba Fix: improve constructor-super errors for literals (fixes #5449) (Toru Nagashima)

Documentation

a8821a5 Docs: Distinguish examples in rules under Stylistic Issues part 2 (Kenneth Williams)
37239b1 Docs: Add new members of the team (Ilya Volodin)
882d199 Docs: Improve options description in no-redeclare (alberto)
6a71ceb Docs: Improve options description in no-params-reassign (alberto)
a959063 Docs: Remove link to deprecated ESLintTester project (refs #3110) (Trey Thomas)
6f88546 Docs: Use double quotes for better Win compatibility (fixes #5796) (alberto)
c94e74e Docs: Make rule descriptions more consistent (Kenneth Williams)
6028252 Docs: Distinguish examples in rules under Stylistic Issues part 1 (Mark Pedrotti)
f1f1dd7 Docs: Add @pedrottimark as a committer (Brandon Mills)
41db670 Docs: Clarify disable inline comments (Kai Cataldo)
9c9a295 Docs: Add note about shell vs node glob parameters in cli (alberto)
5308ff9 Docs: Add code backticks to sentence in fixable rules (Mark Pedrotti)
965ec06 Docs: fix the examples for space-before-function-paren. (Craig Silverstein)

Welcoming JSCS To ESLint

Thu, 14 Apr 2016 17:13:45 +0000

Welcoming JSCS to ESLint

ESLint and JSCS started out at roughly the same time, just three weeks apart in 2013. Both teams had a similar idea: leverage the ecosystem of ESTree-compatible tools such as Esprima to create the next generation of static analysis tools for JavaScript. While ESLint’s primary goal was to create a linter with pluggable rules, JSCS’s primary goal was to codify style guides for easy verification and fixing. Both projects grew and became popular, and soon, we found ourselves playing catch up with each other for features.

For nearly three years now, both teams have been working on solving the same types of issues: how to share configurations, how to autofix some problems, and how to enable the respective ecosystems to grow and thrive. We’ve been doing a lot of the same work in parallel, and recently the teams met to talk about that. We all came to the conclusion that it would be better to be one team, working together on solving these problems, rather than continuing to compete with one another.

Below you’ll find more details about how we’ll move forward as a single team and our plans for both JSCS and ESLint.

Welcoming the JSCS Team

I’m happy to announce that, effectively immediately, the JSCS team is now part of the ESLint team. I’d like to invite everyone to welcome Marat Dulin, Oleg Gaidarenko, Mike Sherov, Alexej Yaroshevich, and Henry Zhu, and we’re looking forward to working with them all. All of the JSCS team members will be joining ESLint as committers (based on our governance policy) for appreciation of their work on JSCS.

Joel Kemp has decided to focus on other work and won’t be joining ESLint. I, and the rest of the team, would also like to thank Joel for his many contributions to JSCS over the years.

JSCS 3.0.0

Today, JSCS released version 3.0.0, which will be the last major release of JSCS. This version has been rewritten to use a concrete syntax tree (CST) instead of an abstract syntax tree (AST). The concept of a CST has been floating around the JavaScript ecosystem for quite some time, and JSCS 3.0.0 represents the first tool to fully realize the use of a JavaScript CST in production. As such, we really need feedback from the JSCS community relating to this release as it’s quite possible we’ll use either the same or a similar approach in ESLint going forward.

If you’re a current JSCS user, I strongly urge you to upgrade to 3.0.0 and report your experience. The JSCS team will continue to work on JSCS in the near-term, fixing bugs as they are reported.

Making ESLint Work for JSCS Users

We recognize that there is a large and vibrant JSCS user base, and as such, the first goal of the combined ESLint/JSCS team is to make the transition to ESLint easy for JSCS users. To that end, our immediate-term plan includes the following tasks:

Identifying rules that exist in JSCS but are missing in ESLint and creating as many of those rules as we can. (#5856)
Incorporating a way to convert .jscsrc files into .eslintrc files with the goal of having a single command to do this automatically. (#5857)
Creating ESLint shareable configs for the most popular JSCS presets. (#5858)
Expanding ESLint’s autofixing capabilities to fix more problems and try, as much as is possible, to approach the level of autofixing available in JSCS 2.x.
Write documentation to guide JSCS users through transitioning to ESLint. (#5859)

Check out our milestone on the tasks above here.

We expect this effort to take several months, and as such, we still encourage current JSCS users to upgrade to JSCS 3.0.0 and provide feedback to the team. We’ll announce when all of the changes necessary to support JSCS users in ESLint are complete and will start encouraging JSCS users to switch to ESLint at that time.

The Future is Bright

With the new combined ESLint/JSCS team, you can expect a lot more from ESLint in the future. We now have some of the brightest people in the world working on making ESLint the best possible tool for JavaScript syntax analysis. I’m personally very excited about ESLint’s future and tackling some of the more difficult problems like making autofix possible for every rule and incorporating type information into our analysis. We can go a lot further, faster, when we’re all working on the same tool.

Nicholas

ESLint v2.7.0 released

Mon, 04 Apr 2016 00:00:00 +0000

ESLint v2.7.0 released

We just pushed ESLint v2.7.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release. This release was meant to be a patch v2.6.1 release, but the version was incorrectly calculated due to a bug in our release tool.

Bug Fixes

161ddac Fix: remove console.dir (fixes #5770) (Toru Nagashima)
0c33f6a Fix: indent rule uses wrong node for class indent level (fixes #5764) (Paul O’Shannessy)

Documentation

7e80867 Docs: Update sentence in fixable rules (Mark Pedrotti)
4f93c32 Docs: Clarify array-bracket-spacing with newlines (fixes #5768) (alberto)

ESLint - Pluggable JavaScript linter

ESLint v2.11.1 released

ESLint v2.11.1 released

Bug Fixes

Build Related

Documentation

ESLint v2.11.0 released

ESLint v2.11.0 released

Highlights

JSCS Compatibility

New Rules

Features

Enhancements

Bug Fixes

Documentation

Dependency Upgrades

ESLint v2.10.2 released

ESLint v2.10.2 released

Bug Fixes

Documentation

Build Related

ESLint v2.10.1 released

ESLint v2.10.1 released

Highlights

Bug Fixes

ESLint v2.10.0 released

ESLint v2.10.0 released

Highlights

New Rules

New Rule Options

Features

Enhancements

Bug Fixes

Documentation

Build Related

Chores

ESLint v2.9.0 released

ESLint v2.9.0 released

Highlights

Improved Autofix

New Rules

Features

Enhancements

Bug Fixes

Documentation

Dependency Upgrades

Build Related

Chores

ESLint Joins The jQuery Foundation

ESLint Joins the jQuery Foundation

What Is Changing

What Isn’t Changing

A New Beginning

ESLint v2.8.0 released

ESLint v2.8.0 released

Enhancements

Bug Fixes

Documentation

Welcoming JSCS To ESLint

Welcoming JSCS to ESLint

Welcoming the JSCS Team

JSCS 3.0.0

Making ESLint Work for JSCS Users

The Future is Bright

ESLint v2.7.0 released

ESLint v2.7.0 released

Bug Fixes

Documentation