Release with JS IR backend?

[joffrey-bion]

I maintain a library depending on this one, but I currently cannot publish it for IR JS backend just because of this one. Is there anyway this could be built and published with IR backend as well?

[qwwdfsad]

The development and support of this library are unfortunately frozen for an undefined period of time.

The actual maintained version of this library was migrated to Ktor a while ago: https://github.com/ktorio/ktor/tree/master/ktor-io

Alternatively, I'd strongly suggest picking okio as a multiplatform IO library

[joffrey-bion]

If you're looking for multiplatform releases of older versions, you can check ktor-io.

This sentence in the doc made me think the migration had happened the other way around. I thought ktor-io was older.

Alternatively, I'd strongly suggest picking okio as a multiplatform IO library

Good point. I remember trying it at some point but I don't remember why I settled for kotlinx-io in the end. Maybe different encodings support or maybe the API was more convenient. I will reconsider.

Thanks for your answer!

EDIT: it looks like Okio does not support other Charsets than UTF-8 in a multiplatform way, that's probably what prevents me from migrating. I'll take a look at ktor-io too.

[joffrey-bion]

Ironically, Okio also doesn't release IR artifacts at the moment because of a bug in the IR compiler: https://github.com/square/okio/issues/910

[ghost]

The actual maintained version of this library was migrated to Ktor a while ago: https://github.com/ktorio/ktor/tree/master/ktor-io`

@qwwdfsad May I ask why? Kotlin should have at least some official IO abstractions everyone could use instead of writing adapters.

[fzhinkin]

We're rebooting the kotlinx-io development (see https://github.com/Kotlin/kotlinx-io/issues/131), all issues related to the previous versions will be closed. Consider reopening it if the issue remains (or the feature is still missing) in a new version.