Improve lodash imports to reduce size of serverless bundles

[luisherranz]

Summary

Serverless is becoming popular and bundle size is important. This PR avoids importing the whole lodash code, even in the server.

Test plan

Tests pass for ChunkExtractor.js, the only affected file.

[gregberge]

I like that, thanks @luisherranz!

[luisherranz]

That was fast. Thanks @neoziro! :)

[bitttttten]

I am not sure what this fixed for you @luisherranz because serverless will still install and include the entire lodash library inside the lambda since the dependencies inside @loadable/server's package.json didn't change.

Wouldn't you want to remove lodash, and install lodash.uniq, lodash.uniqBy and lodash.flatMap? Maybe I am missing something :)

[luisherranz]

@bitttttten it works if you build your bundle using webpack or ncc but I agree that maybe adding them as packages may cover more cases.

[bitttttten]

Ohh I see. I am not using webpack to bundle my lambdas! To be honest I didn't ever think of doing that. I guess that answers my question, thanks!

If you bundle your lambda with webpack, then wouldn't you loose all the niceties of the console editor? Or does it some how keep all that?

[luisherranz]

I'm not familiar with AWS because I use other service. If code don't need to be bundled, then maybe it's not a good idea to make it necessary if someone is using loadable component.

Could you please describe what is the normal workflow in AWS?

[ScriptedAlchemy]

use webpack alias to resolve dependencies

[theKashey]

use webpack externals to keep node_modules in node_modules

[ScriptedAlchemy]

Can you run require on a lambda? And require node modules on that side?

[theKashey]

Of course, you can. Majority of lambdas(they were not created just for SSR task) are written in pure nodejs, and haven't ever experienced any bundler.