Skip to content

1.0.0 doesn't publish wasmJs properly #134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
TheKeeperOfPie opened this issue Feb 28, 2025 · 2 comments
Open

1.0.0 doesn't publish wasmJs properly #134

TheKeeperOfPie opened this issue Feb 28, 2025 · 2 comments

Comments

@TheKeeperOfPie
Copy link

Tried to update from 0.7.0 to 1.0.0 in a wasmJs target and it fails to resolve the platform specific dependency:

 > Could not resolve io.github.petertrr.kotlin-multiplatform-diff:kotlin-multiplatform-diff-js:1.0.0.
     Required by:
         project :modules:entry > io.github.petertrr:kotlin-multiplatform-diff:1.0.0
      > No matching variant of io.github.petertrr.kotlin-multiplatform-diff:kotlin-multiplatform-diff-js:1.0.0 was found. The consumer was configured to find a library for use during 'kotlin-runtime', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.js.public.package.json' with value 'public-package-json', attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm', attribute 'org.jetbrains.kotlin.wasm.target' with value 'js' but:
          - Variant 'jsApiElements-published' declares a library:
              - Incompatible because this component declares a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js' and the consumer needed a component for use during 'kotlin-runtime', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
                  - Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
                  - Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
          - Variant 'jsRuntimeElements-published' declares a library for use during 'kotlin-runtime':
              - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
                  - Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
                  - Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
          - Variant 'jsSourcesElements-published' declares a component for use during 'kotlin-runtime':
              - Incompatible because this component declares documentation, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js' and the consumer needed a library, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm'
              - Other compatible attributes:
                  - Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
                  - Doesn't say anything about org.jetbrains.kotlin.js.public.package.json (required 'public-package-json')
                  - Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
@petertrr
Copy link
Owner

petertrr commented Mar 2, 2025

Hi @TheKeeperOfPie, thanks for the report! When browsing the artifacts at https://repo1.maven.org/maven2/io/github/petertrr, I don't seem to see any differences in js or wasm-js artifacts between 0.7.0 and 1.0.0.
Could you share your Gradle config / minimal reproducer?

@lppedd
Copy link
Contributor

lppedd commented Mar 18, 2025

Is this still reproducible @TheKeeperOfPie?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants