Growth could consider developing its Vue components in an external library (outside of MW) similar to how Codex is developed. This would allow a couple of benefits: components could be written in a standard way, you could use Typescript and other front-end build tools like Vite; you could compile your components for use inside of MW but also deploy a stand-alone documentation site using something like Vitepress, and you could split out your CSS styles into a separate file that you could load independently. If Growth has a large-enough amount of custom components, this approach might be worth exploring. In this situation a lot of the existing Codex Vite configuration could be re-used, and DST could help you with initial setup.
Those benefits sound nice to me. And it is relevant to the proposed work for Growth's engineering intern, where their work would be centered in building Vue/Codex applications independent of MediaWiki.
I would like to propose that we do a spike of e.g. 8 hours to see about setting this up in our repository.