title: node browserify for node core libraries
body: <p>This is a question just to confirm my understanding of node browserify.</p>
  
  <p><a href="https://github.com/substack/node-browserify" rel="nofollow">substack/node-browserify</a> says:</p>
  
  <blockquote>
    <p>compatibility: Many npm modules that don't do IO will just work after
    being browserified. Others take more work. Many node built-in modules
    have been wrapped to work in the browser, but only when you explicitly
    require() or use their functionality.</p>
  </blockquote>
  
  <p>--</p>
  
  <blockquote>
    <p>get browser versions of the node core libraries events, stream, path,
    url, assert, buffer, util, querystring, http, vm, and crypto when you
    require() them</p>
  </blockquote>
  
  <p>Does node browserify takes the source-code of the node build-in modules, and construct a bundled file; by selecting the current working NVM version properly?</p>
  
  <p>Actually, I used browserify first time with <a href="https://github.com/maxogden/websocket-stream" rel="nofollow">maxogden/websocket-stream</a>, and works amazingly.</p>