0.1.13 fails with new JS plugin

[altavir]

ERROR in .._imported/kotlinx-io/0.1.13/kotlinx-io.js
Module not found: Error: Can't resolve 'text-encoding' in 'D:\Work\Projects\dataforge-core\build\js\packages_imported\kotlinx-io\0.1.13'

[JesseCorbett]

I'm running into this issue as well. It's resulting in ktor-js being entirely unusable for me. Any odds we can see this issue addressed soon?

[altavir]

The workaround is to add api(npm("text-encoding")) to JS platform dependencies. It gives a warning about unmaintained dependency, but works.

[Ribesg]

Just encountered this as well!

[dhakehurst]

me too.
Thanks to @altavir for the work-around tip.
I find that I solved this in two parts,
for the browser,
add to package.json

"browser": {
    "text-encoding": false,
    "ws": false,
    "fs": false,
    "path": false,
    "os": false,
    "crypto": false,
    "stream": false,
    "http": false,
    "tls": false,
    "zlib": false,
    "https": false,
    "net": false
  }

then for the tests (which fail also with this problem)

kotlin {
    sourceSets {
        val jsTest by getting {
            dependencies {
                api(npm("text-encoding"))
            }
        }
    }
}

[gincwang]

Hello I'm trying to add this to my gradle (in groovy) but it's not recognizing the npm command, is that another plugin we have to add? Could not get unknown property 'npm' for object of type org.jetbrains.kotlin.gradle.plugin.mpp.DefaultKotlinDependencyHandler

[gincwang]

nvm I got it working with this syntax for groovy

jsMain {
    dependencies {
        implementation npm("text-encoding", 0.7.0)
    }
}

[joffrey-bion]

I had the same issue and added the npm() dependency. It solved the problem, but the warning is a bit annoying.

I actually found out that my own mutliplatform libraries don't publish their npm dependencies either, and require the users to add the npm dependencies to their gradle files just like this.

Is it a gradle plugin issue or should it be fixed in the library?
Any idea how this should be fixed on library side?

[fzhinkin]

We're rebooting the kotlinx-io development (see #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.