title: Bests practice for Browserify in large web projects - Gulp
body: <p>Here is the thing,</p>
  
  <p>I come from a world where you have <strong>several js files</strong> included to a web page. <strong>Some are always</strong> included in the page (your libs, menu etc...) and <strong>others are depending on the current page</strong> (js for login page, js for subscription etc...). 
  Basically let's say that I have <strong>1 different js file per page</strong> plus the libs.</p>
  
  <p>Now I want to start a <strong>new project with browserify</strong> and I am in front of a big problem :</p>
  
  <ul>
  <li>In all the examples I have seen, there is always <strong>a single entry point</strong> (like app.js).</li>
  <li>In my case I would have <strong>n entry points</strong> (1 per page).</li>
  </ul>
  
  <p><strong>So my questions are</strong>:</p>
  
  <ul>
  <li>Is it against good practices to have 1 entry point per page ? Why ?
  <ul>
  <li><strong>If Yes</strong>, What is the good practice for browserifying a large app with lot of page-specific JS ?</li>
  <li><strong>If No</strong>, How to automate that with Gulp. In every examples I found. You have to know the name of every files and process it one after another. (Which is very annoying in a large project with hundreds of pages for example)</li>
  </ul></li>
  <li>How are you dealing with this in your projects ? Do I have to completely rethink my way to deal with page-specific JS code ?</li>
  </ul>