Kotlin/JS 1.9: it looks like `disableGranularWorks...

# eap

[bod]

Kotlin/JS 1.9: it looks like disableGranularWorkspaces (introduced here) no longer exists? Looks like that's why I get asked to execute kotlinUpgradeYarnLock several times, depending on which module I've run my tests last.

[tapchicoma]

cc @Ilya Goncharov [JB]

[Ilya Goncharov [JB]]

In 1.9.0 this behaviour with disabled granular workspaces is going to be default to be sure of yarn.lock consistence

https://github.com/JetBrains/kotlin/blob/494a61a507be7810679d955ad1bdec71ba7a685b/[…]otlin/org/jetbrains/kotlin/gradle/targets/js/yarn/YarnPlugin.kt

[bod]

thanks for replying! But I'm not sure how to proceed. Does it mean that in a multi module project we now need one yarn.lock file per module maybe?

[Ilya Goncharov [JB]]

No, in fact it should be just like earlier with disableGranularWorkspaces, one yarn.lock containing dependencies from all modules

Do you have reproducer of such behaviour? I just check on my simple sample and it works like expected with full list of dependencies in yarn.lock

[bod]

No, in fact it should be just like earlier with disableGranularWorkspaces, one yarn.lock containing dependencies from all modules

Ah interesting!

All right, I'll try to make a reproducer.

[bod]

I've just created https://youtrack.jetbrains.com/issue/KT-59004

[Ilya Goncharov [JB]]

Thank you
I am investigating, now I found that looks like some composite build issue. But I could not minimize sample for now, will continue

[bod]

Yeah I'm sorry I didn't make a smaller project for the reproducer 😅. And yeah I guessed a bit later that it may probably be a composite build issue (I think composite builds are not that commonly used so they often are less tested - for instance we had long standing issues with the the Kotlin IJ plugin and Kotlin Gradle plugin)

[Ilya Goncharov [JB]]

Thank you, I have found the root cause, looks like it have been fixed in “next” Kotlin version, but was not backported into 1.9.0
So I am working on it