Fields pull in all of lodash

var _ = require('lodash');

Lodash is huge (520k), and we’re only using a tiny part of it. The field types shouldn’t be pulling in the entire lodash library. (Its smaller if its minified, but we aren’t minifying it - see #2825).

[JedWatson]

(to be clear, that means I’m closing this because it should be fixed!)

It also speeds up our runtime bundle build too 😃

[JedWatson]

We’ve spent enough effort keeping 0.4 compatible with 0.12 that at this point, I don’t see it as being relatively much of an issue to leave things as they are for that release. As soon as that happens and it’s stable, we’ll be doing a big round cleanup w/ some breaking changes for 0.5, and I’m all for going to Node 4+ then.

Realistically Keystone should have been called 1.0.0 when 0.3 was released, my bad that we didn’t do that but we should think of it as having that level of stability. Let’s use the next few minors to get through some big stuff we’ve got queued quickly, and hit 1.0.0 as soon as we’ve actually thought through and published APIs for stuff we’d like to support for the next year (or whatever time period makes sense)

I’ve added lodash to our common scripts bundle, which means it’ll now be excluded from all the other client side builds (I thought it was there, but must have missed it)

That has the effect of removing the complete package from any bundle, unless we use explicit imports like require('lodash/mapValues') (that will actually currently have the effect of bundling more client side code if we do that, because it won’t be recognised as a package to exclude)