Return to Answer

Yes, it seems like VS 2019 (16.10.0) does not take into account the global %USERPROFILE%\.eslintrc (at least, it does not respect parserOptions.ecmaVersion and parserOptions.sourceType), perhaps because of the conflict of typescript versions in the local (4.3.2) and %LOCALAPPDATA%\Microsoft\TypeScript\ESLint (3.7.4) folders. I created a local .eslintrc.json file in the project root with simple configuration, and id did the trick for me:

{
"parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
},
"env": {
    "es6": true
}

}

No mentioning eslint in local package.json, no local eslint in node_modules! VS uses its global ESLint modules and its default config. Beware that VS resets its ESLint\package.json to initial if you try to update versions of the modules in it!

PS. This approach does not work if parserOptions.project is specified in local .eslintrc file: eslint does not understand ECMA2015 module import again, despite tsconfig module and target options

PPS. ESLint does not process files other than .tsx? or .jsx? when runs under VS IDE (eg .vue) And I have not found how exactly VS runs eslint and passes arguments to it. It obviously uses typescriptlinting.all.js, but it is vague

Yes, it seems like VS 2019 (16.10.0) does not take into account the global %USERPROFILE%\.eslintrc (at least, it does not respect parserOptions.ecmaVersion and parserOptions.sourceType), perhaps because of the conflict of typescript versions in the local (4.3.2) and %LOCALAPPDATA%\Microsoft\TypeScript\ESLint (3.7.4) folders.

I created a local .eslintrc.json file in the project root with simple configuration, and id did the trick for me:

{
    "parserOptions": {
        "ecmaVersion": 6,
        "sourceType": "module"
    },
    "env": {
        "es6": true
    }
}

No mentioning eslint in local package.json, no local eslint in node_modules! VS uses its global ESLint modules and its default config. Beware that VS resets its ESLint\package.json to initial if you try to update versions of the modules in it!

PS. This approach does not work if parserOptions.project is specified in local .eslintrc file: eslint does not understand ECMA2015 module import again, despite tsconfig module and target options

PPS. ESLint does not process files other than .tsx? or .jsx? when runs under VS IDE (eg .vue) And I have not found how exactly VS runs eslint and passes arguments to it. It obviously uses typescriptlinting.all.js, but it is vague

Yes, it seems like VS 2019 (16.10.0) does not take into account the global %USERPROFILE%\.eslintrc (at least, it does not respect parserOptions.ecmaVersion and parserOptions.sourceType), perhaps because of the conflict of typescript versions in the local (4.3.2) and %LOCALAPPDATA%\Microsoft\TypeScript\ESLint (3.7.4) folders. I created a local .eslintrc.json file in the project root with simple configuration, and id did the trick for me:

{
"parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
},
"env": {
    "es6": true
}

}

No mentioning eslint in local package.json, no local eslint in node_modules! VS uses its global ESLint modules and its default config. Beware that VS resets its ESLint\package.json to initial if you try to update versions of the modules in it!

PS. This approach does not work if parserOptions.project is specified in local .eslintrc file: eslint does not understand ECMA2015 module import again, despite tsconfig module and target options

Yes, it seems like VS 2019 (16.10.0) does not take into account the global %USERPROFILE%\.eslintrc (at least, it does not respect parserOptions.ecmaVersion and parserOptions.sourceType), perhaps because of the conflict of typescript versions in the local (4.3.2) and %LOCALAPPDATA%\Microsoft\TypeScript\ESLint (3.7.4) folders. I created a local .eslintrc.json file in the project root with simple configuration, and id did the trick for me:

{
"parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
},
"env": {
    "es6": true
}

}

No mentioning eslint in local package.json, no local eslint in node_modules! VS uses its global ESLint modules and its default config. Beware that VS resets its ESLint\package.json to initial if you try to update versions of the modules in it!

PS. This approach does not work if parserOptions.project is specified in local .eslintrc file: eslint does not understand ECMA2015 module import again, despite tsconfig module and target options

PPS. ESLint does not process files other than .tsx? or .jsx? when runs under VS IDE (eg .vue) And I have not found how exactly VS runs eslint and passes arguments to it. It obviously uses typescriptlinting.all.js, but it is vague

Yes, it seems like VS 2019 (16.10.0) does not take into account the global %USERPROFILE%\.eslintrc (at least, it does not respect parserOptions.ecmaVersion and parserOptions.sourceType), perhaps because of the conflict of typescript versions in the local (4.3.2) and %LOCALAPPDATA%\Microsoft\TypeScript\ESLint (3.7.4) folders. I created a local .eslintrc.json file in the project root with simple configuration, and id did the trick for me:

{
"parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
},
"env": {
    "es6": true
}

}

No mentioning eslint in local package.json, no local eslint in node_modules! VS uses its global ESLint modules and its default config. Beware that VS resets its ESLint\package.json to initial if you try to update versions of the modules in it!

PS. This approach does not work if parserOptions.project is specified in local .eslintrc file: eslint does not understand ECMA2015 module import again

Yes, it seems like VS 2019 (16.10.0) does not take into account the global %USERPROFILE%\.eslintrc (at least, it does not respect parserOptions.ecmaVersion and parserOptions.sourceType), perhaps because of the conflict of typescript versions in the local (4.3.2) and %LOCALAPPDATA%\Microsoft\TypeScript\ESLint (3.7.4) folders. I created a local .eslintrc.json file in the project root with simple configuration, and id did the trick for me:

{
"parserOptions": {
    "ecmaVersion": 6,
    "sourceType": "module"
},
"env": {
    "es6": true
}

}

No mentioning eslint in local package.json, no local eslint in node_modules! VS uses its global ESLint modules and its default config. Beware that VS resets its ESLint\package.json to initial if you try to update versions of the modules in it!

PS. This approach does not work if parserOptions.project is specified in local .eslintrc file: eslint does not understand ECMA2015 module import again, despite tsconfig module and target options