Is it just me, or is 1.3.1 very unstable? I get `F...

# compose-web

[CLOVIS]

Is it just me, or is 1.3.1 very unstable? I get Foo$composable is not defined or IllegalStateException: invalid applier every other build, it's irritating

[Oleksandr Karpovich [JB]]

Not the best advice, but might be worth trying:

<http://kotlin.incremental.js.ir|kotlin.incremental.js.ir>=false in your gradle.properties

[CLOVIS]

Doesn't seem to change much… Do you know where I should report this / what info would help?

The repository is public, so at least reproduction is easy, but it's not exactly minimal.

[Oleksandr Karpovich [JB]]

https://github.com/JetBrains/compose-multiplatform/issues - here

Do you notice such an issue in a project with compose?
Have you noticed the same issue in k/js projects without compose?

[CLOVIS]

The only project I have noticed this in uses Compose for Web (DOM). I have other projects with Kotlin/JS and Kotlin/Multiplatform with JS, and they do not seem impacted (but they do not use Compose)

[CLOVIS]

The most recent modifications which may be related:
• Kotlin 1.7.20 → 1.8.10
• Compose-jb 1.2.2 → 1.3.1
• Enabled the Build Cache
I'm not sure if it's related to the build cache or not, but I disabled it and still have the issues. I'll created a detailed issue on GitHub, then

[Giorgi]

I had similar issues <XYZ> is not defined

it is hard to reproduce but deleting all build/ folders helped in my case.

[CLOVIS]

Same, I have to delete everything every time it happens. It always happens to the same function though (the first composable function called by the app)