New 1.0.0 update fails WASM/JS builds

1.0.0-RC2 worked fine. On 1.0.0 this only happens for WasmJS builds.

java.lang.AssertionError: Different declarations with the same signatures were detected, but no diagnostics will be reported because none of those declarations have any source location info associated with them. This could happen because the declarations came from an external module, or were generated by a compiler plugin. The following declarations have conflicting signatures:
 - FUN name:injectedparams_io_liveselect_app_core_data_AdminRepository visibility:public modality:FINAL <> (supabaseClient:io.github.jan.supabase.SupabaseClient) returnType:kotlin.Unit
 - FUN name:injectedparams_io_liveselect_app_core_data_AdminRepository visibility:public modality:FINAL <> (supabaseClient:io.github.jan.supabase.SupabaseClient) returnType:kotlin.Unit

	at org.jetbrains.kotlin.backend.common.linkage.issues.SignatureClashDetector.reportSignatureClashTo(SignatureClashDetector.kt:71)
	at org.jetbrains.kotlin.backend.common.diagnostics.IdSignatureClashDetector.reportSignatureConflict(IdSignatureClashDetector.kt:20)
	at org.jetbrains.kotlin.backend.common.diagnostics.IdSignatureClashDetector.reportSignatureConflict(IdSignatureClashDetector.kt:14)
	at org.jetbrains.kotlin.backend.common.linkage.issues.SignatureClashDetector.reportErrorsTo(SignatureClashDetector.kt:53)
	at org.jetbrains.kotlin.backend.common.serialization.IrModuleSerializer.serializedIrModule(IrModuleSerializer.kt:49)
	at org.jetbrains.kotlin.backend.common.serialization.SerializeModuleIntoKlibKt.serializeModuleIntoKlib(serializeModuleIntoKlib.kt:122)
	at org.jetbrains.kotlin.ir.backend.js.KlibKt.serializeModuleIntoKlib(klib.kt:512)
	at org.jetbrains.kotlin.cli.pipeline.web.WebKlibSerializationPipelinePhase.executePhase(WebKlibSerializationPipelinePhase.kt:42)

Start by reproducing the WasmJS build with version 1.0.0 and compare it with 1.0.0-RC2. Inspect the generated declarations for the conflicting AdminRepository signature shown in the trace; done means the 1.0.0 WasmJS build completes without the signature-clash assertion.