Flow using directory "flow-typed" even though I've configured another [lib] value in .flowconfig
<p>My <code>.flowconfig</code> file specifies an alternative lib directory named <code>decls</code>:</p>

<pre><code>$ cat .flowconfig  | grep -A1 libs
[libs]
    decls/
</code></pre>

<p>&hellip; and I have verified that declarations are indeed picked up from there.</p>

<p>Yet, the presence of a <code>flow-typed</code> directory created with <a href="https://github.com/flowtype/flow-typed" rel="nofollow noreferrer">flow-typed</a> causes Flow to pick up its definitions from the <code>flow-typed</code> directory instead.</p>

<p>I am using <code>flow-bin</code> version <code>0.27.0</code>.</p>

<p>Reading the main Flow documentation I found no reference to any special handling with respect to the <code>flow-typed</code> directory. The only reference to its special status is given in the the <a href="https://flowtype.org/docs/third-party.html" rel="nofollow noreferrer">third party documentation page for flow-typed</a> where the wording clearly states that a different directory can be used by changing the <code>lib</code> configuration in <code>.flowconfig</code>:</p>

<blockquote>
  <p>If you need to customize the directory where libdefs are stored in
  your project, you can do so by adding a [libs] configuration to your
  .flowconfig file:</p>
</blockquote>

<p>Is the behaviour I am observing a bug or is it a feature that Flow will always use directory <code>flow-typed</code> (if it exists) regardless of the <code>[lib]</code> setting in <code>.flowconfig</code> ?</p>