manage bootstrap using npm

[wenzowski]

This effectively reverts the approach of af8c522
keeping the spirit I see behind d2823ab
that is, managing twbs using npm will be
easier to maintain.

Redistributing the minified file prevents
another repo-moved fiasco like #16, while listing
bootstrap as a devDependency means that developers
will be able to peruse the same version of the
unminifed source without it being checked in to
this repository.

[wenzowski]

This is a much smaller change than it appears due to 3 of the files in css being deleted and the bootstrap.min.css file being moved to the location npm installed it at.

[nateps]

Good idea using npm to manage installing.

I'd include all of the css and less files so that people can require them from within d-bootstrap. It should actually be optional whether or not you want to include the css styles, since you might use a custom compiled version of bootstrap from http://getbootstrap.com/customize/ or you might prefer to require the less files for more flexibility. Perhaps the default should change to not include any styles, and there should be options to include the main styles and the theme styles.

[wenzowski]

I'm under the impression that bootstrap is not distributed as an npm package, but is only distributed as a bower package, despite the package.json in the repo. I chose to fetch it directly with git rather than add an additional dependency on bower. Now that I think about this, npm should be using github's release url for the tarball. The tarball is currently 5.6MB.

Since it looks like the less compiler will be packaged with Derby for now, perhaps it would be better for loadStyles to just be passed the less. In combination with a config object for modifying paths, this would be the most flexible.

[wenzowski]

I'd prefer to include styles by default, but agree it is important for customization to be possible.

[wenzowski]

Using the less directly seems most flexible from a customization perspective, but I'll wait on making that change until derbyjs/derby#388 is reviewed.

[wenzowski]

hmm, while grabbing this over git worked fine the npm docs appear to indicate that anything in node_modules won't be included in a release despite the .gitignore. Perhaps bower makes more sense after all...

[wenzowski]

finished reading npm and found bundledDependencies which solves the problem

[re1ro]

@wenzowski @nateps
I think it was implemented in v0.1.3 and can be closed