A modern programming language that makes developers happier.

kotlinlang

Compose HTML user here. It seems like the latest Compose plugin is doing a bunch of stuff I don't need without the ability to opt out of it. Looks like Compose for Web stuff.

It's already at rc03, and I worry that the team might be rushing for a Kotlinconf release. If possible, can there be a way to opt out of these tasks?

See also:

• <https://github.com/JetBrains/compose-multiplatform/issues/4822>
• <https://github.com/JetBrains/compose-multiplatform/issues/4823>

You could consider migrating to the new Compose plugin in Kotlin 2.0 which only sets up the compiler. Then you'd just add all the Compose HTML deps yourself.

I think I saw either some discussion or code around opting out of those tasks. 

Also not a great solution, but could you disable those tasks manually?

For some context, this isn't just my own project here. I'm the author of Kobweb, so I'm trying to also watch out for my users who are, by extension, Compose HTML users as well.

We can help them migrate their own projects of course, if / when a K2 refactor comes along, but it still would be nice not to give users a bad experience before then.

<@U3K6VQZLJ> Disabling a task doesn't remove it from the output, so it's still noisy.

We actually just tested disabling the Skiko task and it does work, although I'm nervous that we'll be playing whack-a-mole as the team continues to make more of these changes down the line. And will it always be safe to disable a task? Since doing so might end up screwing up with assumptions that the team is making from other tasks.

I do understand that Compose HTML is not prioritized the same as CMP for Web, but I still believe it is considered an official project; as such, it might be nice if the Compose plugin was written with its awareness in mind. I'm assuming the changes here so far are more an oversight than an intentional design.

Yeah definitely not the best solution. 

I found the code I was referencing and it was for disabling multi module resources, not resources as a whole. 

I agree that it would be nice if there was a supported way to disable them entirely.

Agreed. We'll do what we need to do, but I'd prefer not to layer on hacks if possible.

The JB team replied to both bugs, which I wasn't sure would happen with how busy probably is before KotlinConf. Just wanted to say thanks to them for taking a look and replying!