Vampire
08/18/2020, 2:17 PMnodeJs
target, with 1.3.72 there was a run
task automatically.
Now with 1.4.0 there is no run
task anymore.
You can use binaries.executable()
then you at least get a nodeRun
task, but no run
task.
Is that an expected change?
I cannot remember having seen this in any of the update blog entries.Big Chungus
08/18/2020, 2:18 PMBig Chungus
08/18/2020, 2:18 PMVampire
08/18/2020, 2:21 PMbinaries.executable()
explicitly, yes.
But that there is no run
task anymore?Big Chungus
08/18/2020, 2:26 PMVampire
08/18/2020, 2:27 PMrun
task, even when using binaries.executable()
, right?Vampire
08/18/2020, 2:30 PMVampire
08/18/2020, 2:31 PMIlya Goncharov [JB]
08/18/2020, 2:32 PMrun
task, it is bug, and pleasy youtrack it, I tried it on my sample project, and it existsVampire
08/18/2020, 2:33 PMbinaries.executable()
or so.Vampire
08/18/2020, 2:33 PMVampire
08/18/2020, 2:34 PMbinaries.executable()
will still not cause webpack being configured and run for nodeJs
target, correct?Ilya Goncharov [JB]
08/18/2020, 2:38 PMrun
for nodejs
, webpack is not supported in nodejs
yetVampire
08/18/2020, 2:41 PM@vercel/ncc
run for that, thanksBig Chungus
08/18/2020, 3:36 PMVampire
08/18/2020, 4:11 PMVampire
08/18/2020, 5:39 PMcompileKotlinJs
task is part of the binaries.executable()
condition?
Then however it is implemented, it prevents typesafe accessors in pre-compiled script plugins to be generated. :'-(Vampire
08/18/2020, 6:23 PMcompileKotlinJs
is there even without the binaries.executable()
call, but the accessor is missing anywayIlya Goncharov [JB]
08/18/2020, 6:34 PMkotlin {
js {
...
}
}
It is because you can use both
mode, where you will have compileKotlinJsLegacy
and compileKotlinJsIr
instead of compileKotlinJs
So it is unnecessary to register this taskVampire
08/18/2020, 6:37 PMcompileKotlinJs
that has no actions and depends on both of the others,
then a consumer can always use compileKotlinJs
no matter which mode was chosen. 🙂Vampire
08/18/2020, 6:37 PM