As I understand from this bug - <https://youtrack....
# javascriptm
Mike Dawson
03/27/2023, 4:24 PMAs I understand from this bug - https://youtrack.jetbrains.com/issue/KT-43500 - it seems like IR Javascript compilation fails when dealing with any compileOnly dependency.
Now that the Legacy compiler is deprecated, this would mean that compileOnly dependencies cannot be used for Javascript at all. That seems very unfortunate.
b
Big Chungus
03/27/2023, 4:38 PMWhat's your use-case for such dependencies in js?
m
Mike Dawson
03/27/2023, 4:41 PMMy use case is as follows:
I have created a symbol processor that makes Android's Room work with Kotlin multiplatform (by generating JVM/JS code).
Now I need to be able to use Androidx.room annotations on code that I want to compile on JVM/JS.
So I created a module with copies of those annotations, and included it as a compileOnly dependency.
If I use an implementation dependency, then I would get a duplicate class error.
I think my use case is the standard use case for compileOnly: I want to compile against one implementation, but then be able to use a different implementation at runtime.
b
Big Chungus
03/27/2023, 4:44 PMI see, I think rather than plain copying jvm room annotations, you should create a kmp module that declares expect/actual for those annotations and just typealias them to room annotations on jvm actuals.
This is a solution to your immediate problem and NOT an argument against your use-case for compileOnly dependency support
m
Mike Dawson
03/27/2023, 4:46 PMThanks, I did try going down the expect/actual path - but I hit two big problems:
1. You can't include default values in the expect declaration if you use a typealias. So that means any multiplatform code would have to explicitly specify every argument and defaults wouldn't work
b
Big Chungus
03/27/2023, 4:46 PMAlthough now that I think about it, it might not be an issue with compileOnly, but rather incorrect kmp dependency module that doesn't support all required targets
m
Mike Dawson
03/27/2023, 4:48 PM2. The symbol processor (since 1.7) won't resolve expect/actual annotations by default. The annotation processor author has to do that themselves. So when Room's own annotation processor runs, it won't recognize expect/actual as the same thing
b
Big Chungus
03/27/2023, 4:48 PMLegacy js compiler was known to be very lax when it came to enforcing kmp requirements
Big Chungus
03/27/2023, 4:48 PMWhen room runs it should see only room annotations on jvm. No idea what happens on js
m
Mike Dawson
03/27/2023, 4:48 PMIt definitely isn't an issue with supporting all kmp targets: I used the same code on JVM and JS
Mike Dawson
03/27/2023, 4:49 PMI used a shared source set... e.g. for all non-Android supported targets
b
Big Chungus
03/27/2023, 4:49 PMGot it, I might be wrong then
Big Chungus
03/27/2023, 4:50 PMYou mean without declaring all the targets on shared that the consumer module uses?
m
Mike Dawson
03/27/2023, 4:50 PMSorry I don't understand what you mean "without declaring all target on shared that the consumer module uses?"
b
Big Chungus
03/27/2023, 4:51 PMIn order to use a kmp library, it must declare and be compiled for all the targets that your consumer uses
m
Mike Dawson
03/27/2023, 4:52 PMThat is the case... they are both my projects...
b
Big Chungus
03/27/2023, 4:52 PMFor example if you have a module that declares js and jvm targets, you can only use libs in commonMain that also declare js and jvm
m
Mike Dawson
03/27/2023, 4:52 PMThe module itself compiled for JS(BOTH), JVM, and Android
Mike Dawson
03/27/2023, 4:52 PMthe consumer would compile for Js(legacy), JVM, and Android
b
Big Chungus
03/27/2023, 4:52 PMRegardless if the lib is remote (mavenCentral) or local (module)
m
Mike Dawson
03/27/2023, 4:53 PMBut if I set the consumer to Js(IR) - then I get the same as error as mentioned on the bug report
👍 1
b
Big Chungus
03/27/2023, 4:53 PMGotcha, ignore all I said then. Looks like your kmp setup is correct at the very least 😀
Big Chungus
03/27/2023, 4:54 PMNote that that particular error is very generic and happens in many different cases, not just the ones reported there.
m
Mike Dawson
03/27/2023, 4:54 PMFor now, I could try using exclude on gradle to try and block an implementation dependency from coming into Android
Mike Dawson
03/27/2023, 4:55 PMYes - I see the error itself is quite generic - but what struck me is what I'm doing is exactly the same - using compileOnly for an annotation dependency
b
Big Chungus
03/27/2023, 4:55 PMBig Chungus
03/27/2023, 4:56 PMMy point being to not discount the possibility that your issue might be unrelated
m
Mike Dawson
03/27/2023, 4:56 PMI really hope not - I have spent most of the days working on / trying/ thinking about ways around it.
Mike Dawson
03/27/2023, 4:57 PMI will try using the dependency as an implementation and exclude to avoid it coming onto Android. Not ideal, but could workaround the issue for now. If that works, I'll message back and maybe add to the discussion on the bug report.
b
Big Chungus
03/27/2023, 4:57 PMYou're not alone, lots of people have wasted days on that error
m
Mike Dawson
03/27/2023, 4:58 PMThe bug report does have an attached basic reproduction case... that was done back in Kotlin 1.4 days...
Mike Dawson
03/27/2023, 4:59 PMI think it would be worth testing the reproduction case against Kotlin 1.8 - if it still doing that, then I think it is something that really needs looked at. compile only transitive dependencies are a standard feature, so if IR is now the production system, it should handle that
b
Big Chungus
03/27/2023, 5:03 PMAgreed, especially since IR is in beta already
👍 1
Big Chungus
03/27/2023, 5:05 PMNo, wait. It's stable already since 1.8
m
Mike Dawson
03/27/2023, 5:05 PMLegacy is deprecated as I understand... all Kotlin/JS has to move over to IR
Mike Dawson
03/27/2023, 5:19 PMExclude dependencies feature missing on Kotlin Multiplatform - oh goodie: https://youtrack.jetbrains.com/issue/KT-31340/Exclude-transitive-dependencies-for-project-dependencies
Mike Dawson
03/27/2023, 6:15 PMSure enough - after I remove use of compileOnly in the dependency, the consumer app compiles using IR on Javascript
7 Views