Rethinking Virtual Modules

[BryceRussell]

Currently, the virtual modules created for themes can look something like this:

import { Name, Name, Name } fom "my-theme";

export { default as Name } from "...";
export { default as Name } from "...";
export { default as Name } from "...";

But this pattern can have issues with script/styles leaks. An alternative could be to flatten a virtual module into multiple virtual modules with default exports

import Name fom "my-theme/components/Name.astro";
import Name fom "my-theme/components/Name.astro";
import Name fom "my-theme/components/Name.astro";

export default from "..."

export default from "..."

export default from "..."

This can also be easier to type in some cases. For example, instead of typing images manually with ImageMetadata, we can rely on wildcard module types from Astro to type the image imports.

Things to consider:

• Is the current approach for virtual modules ok?
• What other approaches could Astro Theme Provider use to provide assets inside virtual modules?