sdeleuze
02/10/2023, 5:24 AMkotlin-js-store/yarn.lock
generated when not using JS dependencies in our Kotlin/Wasm projects? I guess I am not the only one using Kotlin/Wasm to avoid dealing with the crazy JS ecosystem so getting that thing generated (and expected ti be committed for apps I think) by default is a bit irritating.hfhbd
02/10/2023, 11:17 AMplugins.withType<org.jetbrains.kotlin.gradle.targets.js.yarn.YarnPlugin>().configureEach {
extensions.configure<org.jetbrains.kotlin.gradle.targets.js.yarn.YarnRootExtension> {
yarnLockMismatchReport = org.jetbrains.kotlin.gradle.targets.js.yarn.YarnLockMismatchReport.NONE
}
}
And you could also add this:
plugins.withType<org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsRootPlugin>().configureEach {
extensions.configure<org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsRootExtension> {
nodeDownloadBaseUrl = "<https://nodejs.org/download/v8-canary>"
nodeVersion = "20.0.0-v8-canary202212266b2b946a63"
}
}
tasks.withType<org.jetbrains.kotlin.gradle.targets.js.npm.tasks.KotlinNpmInstallTask>().configureEach {
args.add("--ignore-engines")
}
Svyatoslav Kuzmich [JB]
02/10/2023, 11:53 AMIlya Goncharov [JB]
02/10/2023, 11:55 AMkarma
or mocha
still can be used by build.
But it is common approach, that we will try to reduce affect of NPM dependencies on user’s buildsJames Ward
02/10/2023, 4:15 PMsdeleuze
02/12/2023, 9:32 AMyarn.lock
could be moved to build
when only used for tests to avoid people to have to commit it and that would make it less visible to Kotlin/Wasm users? I am not sure it makes sense to commit it for that use case.Svyatoslav Kuzmich [JB]
02/14/2023, 11:53 AM.klib
(Already possible)
Tier 1: produce .wasm
+ .mjs
(And without .mjs
in the future when we support it).
Tier 2: Run or test plain executable in a VM, like browser, node, wasmtime, etc. This is where you would need to either specify installed VM or download specified version automatically.
Tier 3: NPM, Yarn, warg? integration - should be hopefully orthogonal to compiler tasks