title: ESlint - import.meta causes Fatal Parsing Error
body: <p>Using the <a href="https://atom.io/" rel="noreferrer">Atom</a> editor, with the <a href="https://atom.io/packages/linter-eslint" rel="noreferrer">linter-eslint</a> package installed, I have a node.mjs script that uses ES6 module's <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import" rel="noreferrer">import</a> statement to import various node modules.</p>
  
  <p>The script runs fine when I run it with node's <a href="https://nodejs.org/api/esm.html#esm_enabling" rel="noreferrer">--experimental-modules</a> flag. However, while editing with Atom, linter-eslint says:</p>
  
  <pre><code>Parsing error: Unexpected token import (Fatal)
  </code></pre>
  
  <p>This parsing error is <strong>NOT</strong> being caused by the ecmascript "import" statements that I have at the top of my code file. Instead, it is actually caused by the fact that eslint considers "import" a reserved token that can only be used in <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import" rel="noreferrer">import statements</a> and therefore cannot be used by the <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import.meta" rel="noreferrer">import.meta</a> object (as shown in this code line below):</p>
  
  <pre><code>const __dirname = path.dirname(new URL(import.meta.url).pathname);
  </code></pre>
  
  <p>My .eslintrc.js file has these parser options:</p>
  
  <pre><code>'parserOptions':
  {
      'ecmaVersion': 2018,
      'sourceType': 'module'
  }
  </code></pre>
  
  <p>How can I configure eslint to ignore this particular error?</p>