title: Managing typescript project monorepo with yarn and ts 3.0
body: <p>I've had following react native monorepo structure for a while now</p>
  
  <pre><code>/app
    package.json
  /firebase
    /functions
      tsconfig.json
      package.json
  /types
    package.json
  /ios
  /android
  tsconfig.json
  </code></pre>
  
  <p><code>ios</code> and <code>android</code> folders are respective native code, so we don't really care about them, just included here for nore complete example.</p>
  
  <p>Actual projects are:</p>
  
  <p><code>app</code> - app logic</p>
  
  <p><code>firebase/functions</code> - backend logic</p>
  
  <p><code>types</code> - interfaces of models and stores</p>
  
  <p>each has <code>package.json</code> file with name attribute like <code>@MyCompany/app</code>. This is done for <a href="https://yarnpkg.com/lang/en/docs/cli/workspace/" rel="noreferrer">yarn workspaces</a> and allows me to easily import things between projects.</p>
  
  <p>Thus far it was good and now typescript 3 came out and I want to see if there is a way to clean this up?</p>
  
  <p>At the moment I have 2 <code>tsconfig</code> files, I believe I can somehow merge them into one?</p>
  
  <p>Also, is there a way for me to define multiple <code>.d.ts</code> files instead of my <code>types</code> filder and make my model and store interfaces avaliable globally across projects somehow?</p>
  
  <p>If I use typescript 3, do I need to keep yarn workspaces? These projects are not published anywhere, but deployed to different targets</p>