I gave version 0.91.0 a try, which I believe includes the newly added Node.js support, but kept getting the following syntax error: Identifier 'appendChild' has already been declared.

I wondered why you didn't see such an error, and it turns out that it only occurs in my project when the js target is set to "es2015":

js {
    compilerOptions { target = "es2015" }
    // ...
}

Browsing the source code, my guess is that the compiler is somehow having trouble with these same-name methods (or something similar in another class):

xmlutil/core/base/src/jsMain/kotlin/nl/adaptivity/xmlutil/core/impl/idom/INode.kt

Lines 54 to 57 in c31c4b8

    
           override fun appendChild(node: Node1): INode = appendChild(node.unWrap()) 
        
           override fun appendChild(node: Node2): INode = appendChild(node.unWrap()) 
        
           public fun appendChild(node: INode): INode = appendChild(node.delegate) 
        
           public fun appendChild(newChild: DomNode): INode

I managed to reproduce this is the xmlutil repository by setting the JS target as "es2015" and running the jsNodeTest task, but couldn't figure out a fix (I tried manually specifying @JsName annotations in a few locations).

@pdvrieze, I'd appreciate if you could take a look at this, but we might be dealing with a Kotlin compiler bug. If I get a bit more time anytime soon, I might try to concoct a minimal reproduction for the Kotlin compiler team.

EDIT: Just to add a bit more information about my use-case: I'm using Node when running JS tests during CI with no headless browsers installed, so I set the browser's test task to useMocha(). I was previously ignoring XML-related tests for the JS target, but since xmlutil started supported Node, I thought that I might as well enable those. 😄

NodeJS is missing DOM api. #83

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions