expose options from command line
Everything Whitelisted - Support npm/node dependencies in the browser.

Summary:

- The web server root is now the `src` directory. You can include CSS files
directly from specific component directories under `src` - thanks @chenglou:

  <link rel="stylesheet" href="/core/SiteBoilerPlate.css" />

- Everything whitelisted by default. You can modify `server.js` to include a
blacklist - if packaging/serving takes longer than 100ms for *anyone* we should
absolutely prioritize that feature as a `package.json` config.

- Support for using internal node modules (`util/fs`) - package up browser
versions of these modules with help of awesome npm `browser-builtins` module.
You *must* enable this via the command line switch - it slows down the build
process by about 25ms because it must search all of those files.

- Exposed a nice set of command line switches to `server.js`.

    --useSourceMaps=true
    --useBrowserBuiltins=false     # Allows use of node modules (util/etc)
    --logTiming=true               # Shows colored build timing metrics
    --pageRouteRoot=<root_dir>     # page URLs considered with respect to this.

- Eventually you should never have to touch the `server.js` file.

- Not yet solved including css/images from npm installed dependencies - you can
absolutely install/use/package npm js files, but images are something we have to
think about more.

- Now, just like any standard web server, it just serves files from the `src`
directory - css/images/js/html files - but with the exception that all `.html`
requests look for an existing `.js` react component modlue to render the full
page. `react-page` won't currently server a static `.html` file if it existed in
the `src` directory - but we can easily support that soon.
Merge remote-tracking branch 'origin/master'

Conflicts:
	package.json
	src/elements/Banner/Banner.css