The previous chapter showed us what our Lo-Dash code starts to look like as it falls in place within a larger application. Things get factored into a more generic, reusable form, and they're named and structured consistently. Patterns start to emerge, and as your code starts to realize these patterns, it takes the shape of a production-ready system.

In the spirit of deploying Lo-Dash code to a production environment, this chapter addresses the ecosystem into which our code is tossed when deemed stable. Lo-Dash does a lot, but there are some tasks that this library is simply not well suited for. In other words, it's highly unlikely that Lo-Dash is the only library your application will use.

The best way to keep our code organized and modular is by using modules. Module technology has gained a lot of attention over the last few years in the JavaScript community, and Lo-Dash is no exception. We can make it work using the same module loaders that applications...