title: React.Fragment Error in Visual Studio Code
body: <p>Even though it's working, Visual Studio Code keep displaying error like the screenshot below. AFAIK, my ESLint doesn't seem understand about <code>React.Fragment</code>. It displays error to any <code>&lt;React.Fragment&gt;</code> or <code>&lt;Fragment&gt;</code> that I have.</p>
  
  <p>How to disable or fix this ?</p>
  
  <p>This is an electron-react project, with typescript. I started this project with </p>
  
  <pre><code>electron-forge init my-new-project --template=react-typescript
  </code></pre>
  
  <p>then I updated my <code>react</code>, <code>@types/react</code>, <code>@types/react-dom</code> and <code>react-dom</code> package to their latest version, since I need the <code>&lt;Fragment&gt;</code> component. Fragment is a new feature introduced by React 16.x.x</p>
  
  <p>Here's my current package.json:</p>
  
  <pre><code>"dependencies": {
      "@fortawesome/fontawesome-free": "^5.7.2",
      "@types/prop-types": "^15.7.1",
      "@types/react": "^16.8.17",
      "@types/react-dom": "^16.8.4",
      "electron-compile": "^6.4.4",
      "electron-devtools-installer": "^2.2.4",
      "electron-squirrel-startup": "^1.0.0",
      "electron-stylus": "^0.1.1",
      "ionicons": "^4.5.5",
      "moment": "^2.24.0",
      "prop-types": "^15.7.2",
      "react": "^16.8.6",
      "react-dom": "^16.8.6",
      "react-hot-loader": "^3.1.3",
      "tslib": "^1.9.3"
    },
    "devDependencies": {
      "babel-plugin-transform-async-to-generator": "^6.24.1",
      "babel-preset-env": "^1.7.0",
      "babel-preset-react": "^6.24.1",
      "electron": "^5.0.1",
      "electron-forge": "^5.2.4",
      "electron-prebuilt-compile": "4.0.0",
      "tslint": "^5.16.0",
      "typescript": "^2.2.2"
    }
  </code></pre>
  
  <p>I use VSCode 1.33.1 on Debian machine 64bit, ESLint 1.8.2</p>
  
  <p>error code: </p>
  
  <pre><code>JSX element type 'ReactElement&lt;any, string | ((props: any) =&gt; ReactElement&lt;any, string | ... | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null) | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null' is not a constructor function for JSX elements.
    Type 'ReactElement&lt;any, string | ((props: any) =&gt; ReactElement&lt;any, string | ... | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null) | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt;' is not assignable to type 'Element'.
      Types of property 'type' are incompatible.
        Type 'string | ((props: any) =&gt; ReactElement&lt;any, string | ... | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null) | (new (props: any) =&gt; Component&lt;any, any, any&gt;)' is not assignable to type 'string | ComponentClass&lt;any&gt; | StatelessComponent&lt;any&gt;'.
          Type '(props: any) =&gt; ReactElement&lt;any, string | ... | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null' is not assignable to type 'string | ComponentClass&lt;any&gt; | StatelessComponent&lt;any&gt;'.
            Type '(props: any) =&gt; ReactElement&lt;any, string | ... | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null' is not assignable to type 'StatelessComponent&lt;any&gt;'.
              Type 'ReactElement&lt;any, string | ((props: any) =&gt; ReactElement&lt;any, string | ... | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null) | (new (props: any) =&gt; Component&lt;any, any, any&gt;)&gt; | null' is not assignable to type 'ReactElement&lt;any&gt;'.
                Type 'null' is not assignable to type 'ReactElement&lt;any&gt;'.ts(2605)
  </code></pre>
  
  <p><a href="https://i.stack.imgur.com/deNX7.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/deNX7.png" alt="error in visual studio code"></a></p>
  
  <p>Additional Note: 
  When I import <code>Fragment</code> as a separate variable with: </p>
  
  <pre><code>import * as React from "react";
  import { Fragment } from 'react' 
  </code></pre>
  
  <p>and then try to call the <code>&lt;Fragment&gt;</code> component, It still throwing the same error</p>