title: Will setting "noImplicitAny" in typescript to false disable typechecking?
body: <p>Typescript adds many features on top of javascript es6 and I am interested in <em>static typing</em> and the <em>private/public/protected keywords.</em></p>
  
  <p>The biggest limitation that is imposed by the Typescript compiler so far is the inability to use javascript libraries that do not have type definition files(<code>.d.ts</code>).</p>
  
  <p>We were able to compile against a library(<a href="https://github.com/cheeriojs/cheerio" rel="nofollow noreferrer">cheerio</a>) without type definitions by setting the <code>"noImplicitAny"</code> option to <code>false</code>, but I am concerned that this will allow <em>implicit any</em> in our project's code.</p>
  
  <p>cheerio as well as many other javascript libraries already have type definitions thanks to the <a href="https://github.com/DefinitelyTyped/DefinitelyTyped" rel="nofollow noreferrer">DefinitlyTyped</a> project but I can't predict when we will need a javascript library without available type definitions.</p>
  
  <p>When the need will come we will have to set <code>"noImplicitAny"</code> to <code>false</code>. <strong>Will this effectively disable some or all of the compile time type-checking?</strong> </p>