Bug: running eslint --init generates a .eslint.json file with parserOptions.ecmaversion set to 13

Environment

Node version: v14.17.5 npm version: 6.14.14 Local ESLint version: 7.32.0 Global ESLint version: – Operating System: Ubuntu Linux

What parser are you using?

Default (Espree)

What did you do?

Configuration

{
    "env": {
        "commonjs": true,
        "es2021": true,
        "node": true
    },
    "extends": [
        "standard"
    ],
    "parserOptions": {
        "ecmaVersion": 13
    },
    "rules": {
    }
}

function hello() {
  console.log('hello')
}

Configuration is result from running npx eslint --init after installing eslint locally in an empty project.

Eslint shows an error at the first line of function shown saying Parsing error: Invalid ecmaVersion.

What did you expect to happen?

When running npx eslint --init I expect that it generates an .eslintrc file with valid options. According to documentation, supported options for parserOptions.ecmaVersion are 3, 5 (default), 6, 7, 8, 9, 10, 11, or 12 .

What actually happened?

npx eslint --init generated an .eslintrc file with parserOptions.ecmaVersion set to 13.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

Would love to help if anything. Just not sure where to start.

[aladdin-add]

yes, I think the issue has been fixed in the new package, and the docs will be updated in https://github.com/eslint/eslint/pull/15150 (likely to be merged soon).

[aladdin-add]

@vicasas we are working on a new cli @eslint/create-config to replace eslint --init. it will be fixed in the new repo, please follow https://github.com/eslint/eslint/issues/14768 .