Interesting I ve just been trying to upgrade to 5 4 from 5 2

Question

Interesting I ve just been trying to upgrade to 5 4 from 5 2 and kept getting a NOT FOUND type error 5 3 works Wonder what I am doing wrong

Gunslingor · Answer

i e changing a 2 to 3 works fine changing it to a four gives ```Warning lt i gt lt b gt project srcFrontend Unable to build Kotlin project configuration lt b gt Details org gradle internal operations BuildOperationQueueFailure There was a failure while populating the build operation queue Could not resolve all dependencies for configuration srcFrontend npm Caused by org gradle api artifacts ResolveException Could not resolve all dependencies for configuration srcFrontend npm Caused by org gradle internal resolve ModuleVersionResolveException Could not resolve com beust klaxon 5 4 Required by project srcFrontend Caused by org gradle internal component NoMatchingConfigurationSelectionException No matching variant of com beust klaxon 5 4 was found The consumer was configured to find a usage of kotlin runtime of a component as well as attribute org jetbrains kotlin platform type with value js but Variant apiElements capability com beust klaxon 5 4 Incompatible because this component declares an API of a component as well as attribute org jetbrains kotlin platform type with value jvm and the consumer needed a usage of kotlin runtime of a component as well as attribute org jetbrains kotlin platform type with value js Variant runtimeElements capability com beust klaxon 5 4 declares a runtime of a component Incompatible because this component declares a component as well as attribute org jetbrains kotlin platform type with value jvm and the consumer needed a component as well as attribute org jetbrains kotlin platform type with value js lt i gt ```

Gunslingor · Answer

hmmm message at the bottom I think what s happening here is that klaxon 5 3 is compatible with kotlinJS but 5 4 is not for some reason

cedric · Answer

Not sure if you still have an issue or not I haven t tested Klaxon with JS so not really a bug if it doesn t work in that context

Gunslingor · Answer

Yeah I see that now Klaxon is only for JVM targets as far as I can see Might want to clarify the readMe didn t see any mention of targets I heard there was a kotlinx json package that can be used on all targets so I might give that a try on this project Thanks