Allow applying the plugin on modules with unsupported targets

[CharlieTap]

This is a bit of a niche scenario...

Context

Chasm is a library that lets you interact with web assembly through a typesafe kotlin interface. One of chasms "modes" allows you to write kotlin in the wasm source set, and then generate kotlin interface based on the wasm binary produced by the wasm compilation. You can see an example of this here.

What I would like to do is bind the interface and implementation generated by the codegen into the di graph in the jvmMain source set, but I can't currently as the plugin rejects the build once it sees the wasm target. I was able to do this previously using hilt, you can see that here. I've since migrated the example project to metro and I'm working around it by perfoming the bind in the app module itself.

Ask

Would it be possible to specify a subset of the overall targets a kmp module supports in Metros plugin extension?

[ZacSweers]

What would the API for that look like in gradle? Ideally there's a convention for this already with other plugins we could copy

[CharlieTap]

Just in case someone finds this wasm-wasi support was added in this commit which removes the need for this entirely