title: In VS Code Can I Validate my Javascript But Ignore a Specific Typescript Error?
body: <p>I am writing Javascript in Visual Studio Code (not Typescript).  However, I added <code>"checkJs": true</code> ("Enable type checking on JavaScript files") to my <code>compilerOptions</code> in <code>jsconfig.json</code> to enable automatic imports.</p>
  
  <p>Now that I have done that, I'm getting <em>Typescript</em> errors (squiggly lines), for instance:</p>
  
  <blockquote>
    <p>JSX element type 'Foo' does not have any construct or call signatures.  ts(2604)</p>
  </blockquote>
  
  <p>I could remove these by disabling validity checking, but then I'd lose normal Javascript validity checking.</p>
  
  <p>My question is: is it possible to have automatic imports, and <em>Javascript</em> validity checking, but not have <em>Typescript</em> errors in VS Code?  For instance, is there some flag I can set in <code>jsconfig.json</code> to disable errors with "ts" at the end?</p>
  
  <p>And if not, how do I fix Typescript errors in a Javascript file ... without having to adopt Typescript?</p>
  
  <p><strong>EDIT:</strong> Just to help clarify the <em>kind of</em> solution I'm imagining ... let's say we were talking about ESLint here.  Yes I could add a comment at the top of a file to make ESLint ignore that file, but then I lose all linting whatsoever.</p>
  
  <p>I'm more looking for the equivalent of being able to say <code>"ts2604": false</code> or <code>"ts*": false</code> in an <code>.eslintrc</code> file, or something more like that.  In other words, I don't want to adopt Typescript, or lose all type awareness either ... I just want VS Code's great <em>Javascript</em> features, without large chunks of my code being underlined by error/warning messages that I can't do anything about.</p>