NodeJS is missing DOM api.

[lamba92]

When running into NodeJS the dom API are not available. I would recommend a fallback to https://github.com/jsdom/jsdom with a separate artifact for nodejs.

[pdvrieze]

I'm not particularly interested in nodejs (if you are using Kotlin it makes little sense to use it). The main blocker though would be that (beyond the JS ecosystem being a bit bonkers) kotlin multiplatform doesn't really support multiplatform well. If I do something I'd probably do some runtime detection magic that would allow using jsdom at runtime, but work "automagically".

[lamba92]

My usecase would be AWS Lambdas to cope with the cold start issue, but I understand your point. Indeed I would prefer 2 really separated target for JS which is one NodeJS and another the browser in the K/MP model to solve those evil issues.

[pdvrieze]

@lamba92 You may be able to try native for lambda's (they are best on cold start).

[lppedd]

I wonder what you've ended up using for Node @lamba92.
This library would suite me perfectly but the missing piece is really Node.js.

[lppedd]

For context @pdvrieze, I'm developing a multiplatform library that will be consumed by Eclipse plugins, VS Code plugins, and native CLIs.

[pdvrieze]

I can probably make it work using the generic parser/serializer, but it would still be limited as it still doesn't provide dom. Alternatively I may be able to use WASM/WASI as both are properly supported.

[lppedd]

In the past months I developed my own solution using https://github.com/WebReflection/linkedom as DOM replacement under Node.js.
Small lib, and it is performant.

[pdvrieze]

I probably just need to create a way to load the browser dom if available, and the fallback dom if not.

[pdvrieze]

The new release candidate should now support node without using dom. It might work with an alternative dom implementation if it is sufficiently complete (it requires at least a DomParser object).

[lppedd]

Thanks! How did you make it work? (can also point to a commit in case)

I'd like to see if I can reuse linkedom as DOM replacement in Node.

[pdvrieze]

@lppedd The way it works is that it uses the fact that even for the browser it was already possible to use the generic parser. After that I needed to remove some dependencies on DOM for compact fragments and have some mechanism to ignore some dom dependent tests.

The main commit that actually has the DOM code is aaeb118 and

Other commits mainly work to make other parts of the implementation more generic (not hardcode DomReader/DomWriter).

The main files are: core/base/src/jsMain/kotlin/nl/adaptivity/xmlutil/XmlStreaming.js.kt and core/base/src/jsMain/kotlin/nl/adaptivity/xmlutil/core/impl/dom/DOMImplementationImpl.kt

For the needed code see:

xmlutil/core/base/src/jsMain/kotlin/nl/adaptivity/xmlutil/XmlStreaming.js.kt

Lines 124 to 134 in a49e649

	public actual fun newWriter(
	writer: Writer,
	repairNamespaces: Boolean /*= false*/,
	xmlDeclMode: XmlDeclMode /*= XmlDeclMode.None*/,
	): XmlWriter {
	if (jsTypeOf(js("DOMParser")) == "undefined") return newGenericWriter(writer, repairNamespaces, xmlDeclMode)
	val document = xmlStreaming.genericDomImplementation.createDocument()
	@Suppress("DEPRECATION")
	return WriterXmlWriter(writer, DomWriter(document, xmlDeclMode = xmlDeclMode))
	}

You basically need to make sure that DOMParser is available and (by parsing some dummy xml can be used to retrieve a dom implementation).