One major potential improvement we've discussed is changing VueTest to use the externalized version of Codex, rather than using an embedded version. Components should be able to just `require( '@wikimedia/codex' ). This would mean that VueTest uses the version of Codex inside MediaWiki, which would keep it in sync with core and prevent us from having to update Codex in VueTest itself.

In T326897#8616422, @AnneT wrote:

One major potential improvement we've discussed is changing VueTest to use the externalized version of Codex, rather than using an embedded version. Components should be able to just `require( '@wikimedia/codex' ). This would mean that VueTest uses the version of Codex inside MediaWiki, which would keep it in sync with core and prevent us from having to update Codex in VueTest itself.

We were doing this in the past, but we wanted to include on-wiki demos for experimental components (like the initial Dialog component while it was being developed) – this necessitated embedding our own version of Codex separate from the MW-provided build.

Now that Dialog has been released, it would be easy enough to change this *back* (there are currently no experimental components upstream). Maybe we don't anticipate any future cases where we really want to test experimental components inside MW before they are released.

I guess the alternative would be to support both, either within VueTest or in separate extensions. But I'm not sure if that's worth it