DllPlugin: support entrypoint in DLL bundles

Do you want to request a feature or report a bug?


What is the current behavior?

DllPlugin currently only works on library bundles, not entry bundles. That is, it is impossible for a DllPlugin bundle to execute code when it is imported via a script tag into the page, other than to expose its code as a global variable.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

DllPlugin should support also running an entrypoint module in addition to exposing the global library variable.

If this is a feature request, what is motivation or use case for changing the behavior?

My project has a system architecture in which plugins (optional modules) to the system are dynamically enabled by virtue of having a javascript file for the plugin imported into the page. This behavior is non-negotiable in the project for a few reasons, including our testing/CI environment. So, we build one webpack target per plugin, in addition to the webpack target for the core system. Some of these plugins depend on one another at runtime, and we do not wish to duplicate code inside them since we know a priori that they will coexist at runtime and are imported in the correct topologically-sorted order. The DllPlugin solves this nicely, allowing us to declare that modules will be imported at runtime via the manifest lookup. However, plugins are not just libraries, they are bundles with an entry that needs to execute code. We could build two bundles per plugin, one for the library and one for the entrypoint, but that gets messy and has the drawback of being a breaking change for downstream users of the tool.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

webpack version: 2.2

Author: Fantashit

1 thought on “DllPlugin: support entrypoint in DLL bundles

Comments are closed.