Parsing error: Unexpected token `import`

• ESLint Version: 5.10.0
• Node Version: 11.4.0
• npm Version: 6.4.1

What parser (default, Babel-ESLint, etc.) are you using?

Default.

Please show your full configuration:

Configuration

{
  "extends": "eslint",
  "parserOptions":{
    "ecmaVersion": "2018",
    "sourceType": "module"
  }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

// Workaround for `--experimental-modules`
// See <https://nodejs.org/docs/latest/api/esm.html#esm_import_meta>
const __dirname = Path.dirname(new URL(import.meta.url).pathname)

eslint sample.mjs

What did you expect to happen?

A decent report.

What actually happened? Please include the actual, raw output from ESLint.

  3:40  error  Parsing error: Unexpected token import

✖ 1 problem (1 error, 0 warnings)

Are you willing to submit a pull request to fix this bug?

No.

[seamlik]

Now with this config:

{
  "extends": "standard",
  "parser": "babel-eslint"
}

and installing babel-eslint, the error was gone. Thanks for the solution!

Though I personally can’t consider this ticket is resolved. But I’ll leave the decision to you guys.

[kaicataldo]

@seamlik That’s right. Currently, the solution is to use the babel-eslint parser. That being said, there are plans to change babel-eslint to expect babel as a peer dependency. The assumption is that anyone using babel-eslint is also using babel, but you’ve hit a case where that isn’t true.