Alias the es6 env to es2015

The version of ESLint you are using. 3.4.0

The problem you want to solve. ESLint 3.4.0 introduced new preferred numbers for the ecmaVersion property, e.g. 2015 instead od 6. The change is not reflected in the es6 environment name. My current example config is now inconsistent:

module.exports = {
    parserOptions: {
        ecmaVersion: 2016,
    },

    env: {
        es6: true,
    },

    rules: { /* ... */ },
};

Your take on the correct solution to problem. An alias env called es2015 should be created and preferred to the old es6 one.

[michaelficarra]

There’s nothing wrong with the ability to write

env:
  es6: true
  es2015: false

Then the user will just get the error “Both es6 and es2015 env options were set to conflicting values. Remove one to continue.”

[btmills]

Based on discussion in the 2016-09-01 TSC meeting, we believe supporting both es6 and es2015 in parallel or renaming es6 to es2015 would be more confusing than keeping the name as-is. es6 will remain, and we will use year-based naming starting with the 2017 edition. (ES7/ES2016 introduced no new globals, so it doesn’t have its own environment.)