What problem does this feature solve?

We are building multiple micro frontend applications that are then stitched together into singular spa experience at run-time. As such, building these applications in using a build target "--target app" is not a viable approach. We need a single file that contains the application source code to load up as we are stitching applications together. For this reason, using a build target "--target lib" seemed like a ideal solution for us. However, we've noticed the build tool contains logic when it is building the application that it excludes Vue instances automatically, which you folks have clearly indicated in your documentation. We weren't able to override this behavior using either the configureWebpack object nor the chainWebpack() callback function.

What does the proposed API look like?

As simple fix would be to move the process of externalizing Vue up prior to applying configureWebpack config object or executing chainWebpack() callback. That way, you are giving programmers the flexibility to include it if it suits their architectural scenario without it being a breaking change.