Kotlin / Kotlin/dukat

All Node.js definitions are generated (broken) when adding @actions/cache

Open
#397 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Kotlin
Stars
591
Forks
40
PR merge metrics
No merged PRs in 30d

Description

When I added `@actions/cache` here: https://github.com/Vampire/setup-wsl/blob/master/buildSrc/src/main/kotlin/net/kautler/node.gradle.kts#L119, Dukat started to generate definitions for all of Node.js even with me using `kotlinx-nodejs`.
Those generated definitions have many problems and they should probably not be there at all.
Even with `generateExternals = false` they were generated (https://youtrack.jetbrains.com/issue/KT-41232).
My work-around was to delete all generated `*.module_node.kt` files: https://github.com/Vampire/setup-wsl/blob/master/buildSrc/src/main/kotlin/net/kautler/node.gradle.kts#L141-L144

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with buildSrc/src/main/kotlin/net/kautler/node.gradle.kts, especially the @actions/cache dependency and the workaround deleting generated *.module_node.kt files. Reproduce generation with that dependency and compare behavior when generateExternals is false. Done means unwanted Node.js definitions are no longer generated without removing required declarations.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin, node.js
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.