title: How to link tsd definitions automatically with bower and npm?
body: <p>I'm in the process of converting an existing project to TypeScript with many bower and npm dependencies (bower.json and package.json). According to the <a href="https://github.com/DefinitelyTyped/tsd" rel="nofollow">tsd github page</a>, </p>
  
  <blockquote>
    <p>TSD supports discovery and linking of definitions from packages
    installed with node or bower. Use the link command and your tsd.d.ts will be updated with paths to the files in the node_modules or bower_modules folders.</p>
  </blockquote>
  
  <p>However when I run the command <code>tsd link</code> after <code>tsd init</code> it just says <code>no (new)packages to link</code> even though my package.json is chalk full of modules. This led me to discover, maybe it does not do what I think it does. </p>
  
  <blockquote>
    <p>This feature will scan package.json and bower.json files for a
    typescript element. This element then contains definition or
    definitions sub-element that contain relative path(s) to .d.ts files:</p>
  </blockquote>
  
  <p>What? What is the purpose of this <code>link</code> feature if it doesn't just get type definitions from my package.json? Is this command merely to pull tsd configurations from my package.json instead of in my tsd.json file? What then, is the point, other than eliminating the tsd.json file?</p>
  
  <p>So if it's not <code>tsd link</code>, I'm asking if there is any better way to automatically include tsd definitions for all my dependencies. It seems kind of crazy to me that these would all be managed by hand.</p>