Hi! I see that a bunch of methods in the Kotlin Gr...

# javascript

[CLOVIS]

Hi! I see that a bunch of methods in the Kotlin Gradle Plugin have been deprecated relating to Node.

In particular I have this code:

val kotlinEnvironment = project.rootProject.kotlinNodeJsExtension    // ⚠ deprecated
	nodePath.set(
		kotlinEnvironment
			.requireConfigured()                                         // ⚠ deprecated
			.let { RegularFile { File(it.nodeExecutable) } }             // ⚠ deprecated
	)

I'd like to migrate this code to the new way. Basically all it does is find out where the Kotlin plugin installed NodeJS (because we have some other tools that need NodeJS with the exact same version as the Kotlin plugin is using).

From what I can gather:
• project.rootProject.kotlinNodeJsExtension should be not use rootProject anymore and should use an extension related to NodeJsPlugin , but I can't find which exactly
• requireConfigured() should be needed anymore because the new extension takes care of that itself (?)
• nodeExecutable has been replaced by just executable ?
What am I missing?

[CLOVIS]

I'm guessing something like this?

val nodeJsEnvironment = project.extensions.getByType(NodeJsEnvSpec::class.java)
	nodePath.set {
		nodeJsEnvironment
			.installationDirectory
			.asFile.get()
	}

but I'm getting

Unable to load class 'org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsEnvSpec'.

This is an unexpected error. Please file a bug containing the idea.log file.

[Robert Jaros]

Related: https://kotlinlang.slack.com/archives/C0B8L3U69/p1733070789383059

[CLOVIS]

In my case I can't just ignore the error, it crashes on Kotlin 2.1.0

[CLOVIS]

@Ilya Goncharov [JB] you mentioned in the previous thread that something was going to be added?

[Edoardo Luppi]

Does this help?
https://youtrack.jetbrains.com/issue/KT-69628/K-Wasm-Node.js-version-per-project#focus=Change-27-10781519.0-0

[Ilya Goncharov [JB]]

The actual usage will be something like

plugins.withType<org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsPlugin> {
    the<org.jetbrains.kotlin.gradle.targets.js.nodejs.NodeJsEnvSpec>().executable // Provider<String>
}

[CLOVIS]

@Ilya Goncharov [JB] when you say "will be", this isn't yet published, right? I don't see the .executable field in 2.1.0

[Ilya Goncharov [JB]]

Yes, I am afraid that these changes were not released in 2.1.0
But these changes can be seen in master
https://github.com/JetBrains/kotlin/blob/2f8ba6fdff8b1988b38baa583273586d26f33427/libraries/tools/kotlin-gradle-plugin/src/common/kotlin/org/jetbrains/kotlin/gradle/targets/js/AbstractEnvSpec.kt#L58

[CLOVIS]

Are you aware of a workaround until the next version lands? (even if it's not pretty, since a proper fix will come soon)—my plugin fails on all 2.1.0 projects 😅

[Ilya Goncharov [JB]]

Could you suppress deprecations with @Suppress("DEPRECATION"?

[CLOVIS]

@Ilya Goncharov [JB] I could in KGP 2.0.20, but I think the fields are completely gone in KGP 2.1.0? At least IntelliJ can't find where they moved to

[Skaldebane]

Was this addressed with 2.1.10?

[CLOVIS]

NodeJsEnvSpec.executable does not seem to exist in 2.1.10. If I understand the GitHub correctly, it is in 2.1.20-Beta2?

[CLOVIS]

@Ilya Goncharov [JB] I'm trying the solution you mentioned in https://kotlinlang.slack.com/archives/C0B8L3U69/p1736419886059929?thread_ts=1736281644.920429&cid=C0B8L3U69, now that Kotlin 2.1.20 is out, and I'm getting

org.gradle.api.UnknownDomainObjectException: Extension of type 'NodeJsEnvSpec' does not exist. Currently registered extension types: [ExtraPropertiesExtension]

[CLOVIS]

This seems to work, but it's a bit disappointing how convoluted it is.

[CLOVIS]

Ah, it doesn't really work.

- Gradle detected a problem with the following location: '/home/ivan/.gradle/nodejs/node-v22.0.0-linux-x64/bin/node'.
    
    Reason: Task ':app:viteBuild' uses this output of task ':core:kotlinNodeJsSetup' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

I'm confused why :core would have a :kotlinNodeJsSetup , I thought only the root module had that task?

[Shubham Singh]

@Ilya Goncharov [JB] ☝️ Could you please help with this?

[Ilya Goncharov [JB]]

Hi, yes, now Node.js can be configured per project, and it helps to set independent versions of Node.js for different subprojects, if it is necessary
https://youtrack.jetbrains.com/issue/KT-69628/K-Wasm-Node.js-version-per-project

[CLOVIS]

@Ilya Goncharov [JB] There seems to be something configured incorrectly with this feature then.
As you can see in the error message I shared, Gradle detects that :app:viteBuild uses a file generated by :core:kotlinNodeJsSetup , so evidently they don't use separated installations.

[CLOVIS]

Unless I missed something, it seems the only way for this feature to work is if the :app:viteBuild task declares a mustRunAfter on each :xxx:kotlinNodeJsSetup where :xxx is each project that appears in the dependencies of :app