If users install Qt for WebAssembly and immediately try to build something in Qt Creator, nothing really works because the WebAssembly plugin of Qt Creator is experimental, thus not enabled by default. That already caused some confusion and it is quite difficult for the user to figure out by her/himself.

Therefore it would be helpful if the installer component of Qt for WebAssembly automatically called:

var settingsFile = installer.value("QtCreatorInstallerSettingsFile");
component.addOperation("Settings", "path="+settingsFile, "method=add_array_value", "key=Plugins/ForceEnabled", "value=WebAssembly");

... so that the Settings of Qt Creator contains:

[Plugins]
ForceEnabled=WebAssembly

See for a similar task that was implemented a few Months ago for Qt for MCUs: UL-1496 https://codereview.qt-project.org/c/qtsdk/tqtc-qtsdk/+/281997

We also do the same for Qt for WinRT.