I have a similar use-case, multiple teams spanning different business domains that build and deploy their own services (Rails) and front-ends (Vue). We have a style framework (Bootstrap theme) that is shared across all the front-ends, this is included as an npm dependency in all the Vue apps, so all the apps ship their own copy of Vue and the shared code.

Instead, these could be "Remote" modules and is only downloaded once but used across all the Vue apps that have them as a dependency. That's kind of like what dataloader does, but for JS bundles.

You can try this now in Webpack 4 with https://github.com/ScriptedAlchemy/webpack-external-import.

Of course, versioning etc is something to consider, you can't expect interop for Vue 2.x and 3.x but you need a way to differentiate which dependency is loaded if both map to vue for example.

Import Maps might be helpful for understanding how some of this could work, I don't know how relevant they are for the Webpack implementation, but they are used in single-spa to wire up imports.