In T88879#1181799, @Spage wrote:

I think all these patches are merged and deployed on beta labs, but by the time mediawiki.js's execute() is called, there is an empty registry[module].templates object for dozens of module names, so mw.templates still has 70 objects in it, nearly all empty.

Yeah, but they're not sent over the wire. They're created at run time because those fields are of type Object and they must have a value, so they default to empty object.

This isn't specific to templates. Though templates is the only one with a public getter. Inspect mw.loader.moduleRegistry to see many empty arrays for dependencies, for example.

I'm closing this since the redundant parameters are no longer sent in load.php responses. The memory footprint of these objects existing can be evaluated in a separate issue. I believe in most cases we can easily remove these since this is a private structure. However dependencies is a field we look through very frequently and enables native batching as an array. The others (including templates) can probably be removed.

However due to having a public getter it is also the hardest one to remove because right now callers can assume that passing a loaded module's name results in an object that they can try accessing keys on. So we may want to keep that for back-compat in the getter only.