Earlier quoted context omitted.
If you're using CommonJS you can do require('lodash/category/method'), and when it gets built on the frontend it'll only include the method and its dependencies. So if you're using only 5% of lodash, you'll only get that 5%.
Right. If on node, you can also use modules via NPM ( https://www.npmjs.com/browse/keyword/lodash-modularized ). But as I said, this is common in many frameworks. Hell, you can even do with JQuery ( http://projects.jga.me/jquery-builder/ ). So having this ability doesn't make Lodash special. This is not presented as the preferred method to use the framework on the project page either. You just get a link on the front…
There's little upside in hosting a light version, and fragmenting the docs. Min/max'ing on filesize lets you save 15 kB, or 0 kB. Creating a light build that saves 5 kB is a maintenance cost with a poor ratio relative to reward.