Add support for emitting node modules from webpack

[kpdecker]

This has two fold impact:

1. Allows for arbitrary loaders to run in both node and browser environments (Partial for Webpack loader for images to move them to static folder #1825)
2. Optimizes the build time for modules.

Risks:

• Transitions all harmony code to utilize harmony end to end. Previously this had not happened, which may break users in unexpected ways. (See Propagate source maps through combine assets step #2508)
• Require logic changed across the board to utilize node and webpack behaviors where possible, simplifying code, but potentially breaking things in the wild.

This isn't complete, but wanted to open to discuss with collab team.

Open tasks:

• publicPath dynamic path handling (assetPath, etc)
• Move existing webpack code into webpack folder for consistency.
• Further testing, etc

[nelix]

This is really impressive work, I can't really fix all my performance issues with a ton of custom config as well as this can...
The webpack plugins are slightly over my head, it would be awesome if some other people could chime in..

[kpdecker]

This is way out of date with current impl. Going to revisit and reopen.

[lock]

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.