incorporate browserify?

[cugos]

incorporate browserify?

[mapsam]

After #19 we are removing bower from the equation and going to roll with some quick CDNs and begin working on incorporating browserify for module use.

[mapsam]

This is coming up as an issue as people begin looking at #11 and making @aaronr angry!

[alukach]

What does @aaronr think about this?

Why was it that we decided to table browserify in the first place? I don't quite recall. I do like the idea of writing this all node-like in the event that we ever want to make an offline-friendly downloadable DNC.

[ranchodeluxe]

@svmatthews @alukach @aaronr
I think the easiest solution is to only use browserify to require the third-party modules we need and then expose/tag them to the L.DNC namespace. You'll just have to ensure that the browserify build happens at the end of the L.DNC build so the L.DNC namespace is already available.

var shape_package = require('shapefile-lib-thing');

L.DNC.ShapeUtils = shape_package;