Is making a “node exec” task generally available p...

# javascript

[Rob Murdock]

Is making a “node exec” task generally available part of the js plugin plan (for running things installed by an npm dependency)?

I have a few node programs I need to run, but to do that in gradle right now I’m juggling both the kotlin auto-installed node and the “com.github.node-gradle.node” plugin… which seems silly and causes multiple node installs.

[Casey Brooks]

If you have node installed locally, just set up a normal Exec task to run the node commands. Should be easy enough to pass project properties to it for a dynamic “node run” type command

[Rob Murdock]

oh yeah, that sort of thing is easy. But as much as possible I prefer my gradle builds to auto install specific versions of things so in all environments things work the same way

[Rob Murdock]

that technique was where i started years ago 🙂 transitioned to the node gradle plugin to make things more systemized and rely less on environment config… now I’d like to make another jump!

[Robert Jaros]

I'm using this function to get the path of the node binary installed by kotlin plugin:
https://github.com/rjaros/kvision-examples/blob/master/template/build.gradle.kts#L107-L114
and then just use Exec task with executable parameter:
https://github.com/rjaros/kvision-examples/blob/master/template/build.gradle.kts#L161

[Rob Murdock]

not bad!

[Rob Murdock]

I’ll have to give that a shot later. Still hope an official task gets put in down-the-road so there’s less fuss. 😉

[Rob Murdock]

Do you know what the correct tasks are to depend on in order to ensure that the binary is there by runtime? @Robert Jaros

[Robert Jaros]

I'm using dependsOn("kotlinNpmInstall")

[Robert Jaros]

But it's all changing with new Kotlin versions every time lately ... 😉