what is the difference between node and nodejs in the intelliJ gradle plugin?

# gradle

[Gunslingor]

what is the difference between node and nodejs in the intelliJ gradle plugin?

[Ivan Kubyshkin [JetBrains]]

Do you use

id 'org.jetbrains.kotlin.js' version '1.3.71'

?

[Ivan Kubyshkin [JetBrains]]

In that case there is only nodejs as a target

[Ivan Kubyshkin [JetBrains]]

kotlin {
    target {
        nodejs()
    }
}

[Gunslingor]

yeah I do, finally figured that part out, I was using both this and mooworks plugin so I had both. It really isn't clear what plugins are compatable, many of em seem to end in compiled code on drill downs... maybe I can configure intelliJ to drill down into the source code or something?

[Ivan Kubyshkin [JetBrains]]

Do you mean source code of gradle?

[Gunslingor]

Nope, of the plugins themselves. Here are some of the "dead ends" I'm talking about during drill down. Maybe I am missing something about the abstract nature of the first one but it looks like a circular functional dependancy of overloads or something; the second screenshot ends it a compiled code comment that I don't really get fully but suspect I know what is going on there... these are likely class headers just so java knows what to call in the compiled libraries? That's what I mean, I think I recall there is functionality somewhere in intellij where you can use the compiled distros for your app, but you could also import the source material and it would know to drill into that instead of the dead end of compiled code. I though I recall it being a control, something called "mark directory as library root" or something. Really just trying to fill in any gaps in my knowledge... whenever I have to engineer indirectly, often with trial and error, I get very nervous and wonder what I'm missing.