env.es6=false does not disable es6-specific rules

.eslintrc:

{
  "env": {
    "es6": false
  },
  "rules": {
    "no-var": 2
  }
}

index.js:

'use strict';

var test = 1;

global.console.log(test);

$ eslint .

index.js 3:1 error Unexpected var, use let or const instead no-var

It would be desirable to be able to maintain a single shared config that enables ES6 rules such as “no-var”, and use this config with both ES5 and ES6 projects. Ideally, the only difference in ESLint configuration between such projects would be the value of env.es6.

[bsed]

1:1 error Unexpected var, use let or const instead no-var 2:1 error Unexpected var, use let or const instead no-var 3:1 error Unexpected var, use let or const instead no-var 3:5 error ‘favicon’ is defined but never used no-unused-vars 4:1 error Unexpected var, use let or const instead no-var 5:1 error Unexpected var, use let or const instead no-var 6:1 error Unexpected var, use let or const instead no-var 8:1 error Unexpected var, use let or const instead no-var 9:1 error Unexpected var, use let or const instead no-var 11:1 error Unexpected var, use let or const instead no-var

[jokeyrhyme]

I’m using ESLint v1.3.1.

I think the long term solution is to actually generate the rules documentation by parsing each rule’s implementation JavaScript. This means each rule declares which group of rules it belongs in (e.g. “style”, “es6”, etc). From this, ESLint can identify all the ES6 rules and disable them when env.es6 is false.

A short-term solution would be to just explicitly list all the ES6 rules in the code responsible for disabling them. We’d need a strategy for keeping the list up to date, perhaps a unit test that parses the documentation to identify “es6” rules?