title: What is the recommended manifest JSON format for Bower packages?
body: <p>Using the <code>$ bower init</code> command, I have created a <code>bower.json</code> for my package and registered it with Bower, no problem. </p>
  
  <p>After looking at the Github homepages for some popular Bower packages, e.g. <a href="https://github.com/jrburke/requirejs" rel="nofollow">RequireJS</a> and <a href="https://github.com/Modernizr/Modernizr" rel="nofollow">Modernizr</a>, I've noticed their repo's don't contain a <code>bower.json</code> or a <code>component.json</code>. How is this possible?</p>
  
  <p>I've also noticed that when I download any Bower package, the package contains a <code>.bower.json</code> file (note the dot in the beginning) and that file contains quite a bit more information than what I was asked during <code>$ bower init</code> for my package. For example, below is the <code>.bower.json</code> from Modernizr:</p>
  
  <pre><code>{
      "name": "modernizr",
      "homepage": "https://github.com/Modernizr/Modernizr",
      "version": "2.6.2",
      "_release": "2.6.2",
      "_resolution": {
          "type": "version",
          "tag": "v2.6.2",
          "commit": "ca45d02757b83367d8455d477e3cbc42dfdee035"
      },
      "_source": "git://github.com/Modernizr/Modernizr.git",
      "_target": "~2.6.2",
      "_direct": true
  }
  </code></pre>
  
  <p>When I download my newly created package, it just contains the same info that I originally checked in to git.</p>
  
  <p>Is there a new format for <code>bower.json</code> that I should be using? Or did I simply miss something in the setup process?</p>