Pack all dependencies defined in package.json

[miltador]

This will solve various issues with 'implicit' dependencies that aren't directly used in your code but required by other modules.
The developer himself is responsible to moderate the dependencies list and update it accordingly.

[HyperBrain]

I think this PR is counter-productive to the mechanisms and use cases webpack is used for.
When you use wepback, it optimizes the dependencies and removes unneeded ones - this is one of the basic concepts behind it. So only the webpack result states exactly which modules have to be packaged and which not.
Imo the user cannot know, what is needed and what is not.

If you found a problem, please open an issue for it. Then we can discuss it deeply and after it has been discussed how can or should be solved, you can offer a PR for the solution. Just submitting a PR does not offer the right platform for discussions. Especially this change is not trivial, breaking and changes existing functionality.

Nevertheless a big thank you for your contribution 👍 . Please open an issue for the problem.

What I see as a possible improvement in the whole way, the webpack plugin handles the fetching of the npm modules is, that it could retrieve the physical node modules that it packages from the projects node_modules directory instead of using npm to download them on deploy, but that's out of scope for this PR and should be handled and discussed in a separate issue (it is not trivial and has some side-effects).

[HyperBrain]

The packaging of implicit dependencies has been solved recently ( #186 ) and is available in the V3 pre-release version 3.0.0-rc.1.
Now you can bundle node modules by whitelisting them in node-externals and all transient dependencies (implicit dependencies) will be bundled correctly. The needed modules are perfectly detected by webpack after its optimization phase.

[HyperBrain]

Closing this PR now. The package handling has been partly rewritten and improved in V3. If anything should be improved further, we should open an issue for that (feature request), so that it can be phased in correctly.

[miltador]

That's cool! Thanks. I already gave up on AWS but this sounds cool.

[HyperBrain]

BTW: Sorry for the very late responses 😔 . The project was kind of dead from February until we revived it in Juli, but now it's back and I'll try to maintain it as good as possible (including frequent releases, etc.)