how do I access `process` from nodejs? It seems th...

# javascript

[Rohde Fischer]

how do I access process from nodejs? It seems that my kotlinjs in general is very browser-centric, which is kind of frustrating 😕

[Robert Jaros]

Try https://github.com/JetBrains/kotlin-wrappers/tree/master/kotlin-node

[Rohde Fischer]

looks interesting, do I just import, or do I need to use it as a gradle plugin?

[Robert Jaros]

Just add as a dependency and you should have all nodejs declarations ready to use

[Rohde Fischer]

will give it a try, thanks

[Rohde Fischer]

when I'm using it I get: When accessing module declarations from UMD, they must be marked with both @JsModule and @JsNonModule.

[Chrimaeon]

whats your version of the multiplatform plugin?

[Robert Jaros]

I think the declarations are designed to work with useEsModules() option

[Rohde Fischer]

I'll see if that works, I must admit that JS/TS and the various import schemes have always been slightly confusing to me

[Rohde Fischer]

@Chrimaeon 2.1.0

[Rohde Fischer]

@Robert Jaros well now it compiles, but ofc the wrappers I already have is now broken

[Rohde Fischer]

Error: Cannot find module '/home/rohdef/git/action-build-container-source/build/js/node_modules/@docker/actions-toolkit/lib/github' imported from /home/rohdef/git/action-build-container-source/build/js/packages/action-build-container/kotlin/action-build-container.mjs
Did you mean to import "@docker/actions-toolkit/lib/github.js"?

the error I get on the existing imports are like this one. I guess it could change it to refer to the .js files, but isn't that kind of wrong to do?

[Rohde Fischer]

and when running it doing that I get:

Error [ERR_REQUIRE_ESM]: require() of ES Module /home/runner/work/_actions/rohdef/action-build-container/main/node_modules/action-build-container/kotlin/action-build-container.mjs not supported.
Instead change the require of /home/runner/work/_actions/rohdef/action-build-container/main/node_modules/action-build-container/kotlin/action-build-container.mjs to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (/home/runner/work/_actions/rohdef/action-build-container/main/index.js:5:1) {
  code: 'ERR_REQUIRE_ESM'
}

it is not happy with me

[Robert Jaros]

Sorry for that. I really thought kotlin-node project will just work for you.

[Rohde Fischer]

no worries, it was worth a shot 🙂

[Chrimaeon]

and you have configured your target as nodeJs and not browser?

[Edoardo Luppi]

You need to configure a module type, useCommonJs() or useEsModules()

[Edoardo Luppi]

Ah you've already figured it out. I guess you'll have to fix your own wrappers unfortunately 😞

[Robert Jaros]

Perhaps it will work with useCommonJs() (it should allow require, shouldn't it?)

[Edoardo Luppi]

Yup in that case CommonJS is the right pick.

[turansky]

I really thought kotlin-node project will just work for you.

@Robert Jaros we had no control under project dependencies 😉.
kotlin-node support both ESM and CommonJS.
ESM - default recommendation, because it works everywhere (Browser, Node, Deno) and it's future default/single Kotlin/JS option.
CommonJS - can be used if you have problems with dependencies.
Node 23.5.0 already contains pills for mixed projects.

AFAIK @Vampire has pills for CommonJS dependencies in ESM project 😉

[turansky]

Choose dependencies with compatible module system and/or bundler configuration - developer responsibility 🙂

[Vampire]

Do I? :-D

[Vampire]

I just used some case by case regex replacements for specific cases that you gave me. :-)

[Vampire]

https://github.com/Vampire/setup-wsl/blob/master/gradle%2Fbuild-logic%2Fsrc%2Fmain%2Fkotlin%2Fnet%2Fkautler%2Fnode.gradle.kts#L65-L79

[Rohde Fischer]

@Chrimaeon yes, I only configured for nodejs, no browser anywhere 🙂

[Rohde Fischer]

@Edoardo Luppi curious, what is the default if neither is set? That was my point of origin that I more or less reverted to

[Rohde Fischer]

so if I read the thread right, I should be able to make it work using useCommonJs, but in actuality useESModules would be better, if I can figure out to rework that wrappers I already have?

[Rohde Fischer]

the useCommonJs-approach works 🙂

[Vampire]

As far as I understood it, ESM is "the new way" and also the default for normal node js modules. Some dependencies I used were only ESM-compatible in latest version, so I forcibly had to switch to ESM to use the new version.

[Edoardo Luppi]

Node.js predominantly uses CJS, but it can now operate both, and at the same time, with mostly no issues on the ESM side.
Still CJS is what most packages are using.

[Edoardo Luppi]

@Rohde Fischer the default is UMD

[Edoardo Luppi]

The fact ESM still isn't widely used on Node projects is also why I've been pushing for a split between Node and browser in MPP, so that we can configure different module types based on the target.