What problem does this address?

The current iAPI Router implementation simply looks for all JavaScript modules in the HTML and imports them. However, some of them may not be necessary, potentially executing code that is neither related to interactive blocks nor compatible with the Interactivity API.

What is your proposed solution?

We could implement a mechanism that tells the iAPI router which JavaScript modules to consider and which to ignore. Some sort of "allowlist" would be fine.