So after adding this compile option: kotlin { ...

# react

[Mike Kienenberger]

So after adding this compile option:

kotlin {
js(IR) {
compilerOptions {
target.set("es2015")
}
}
}

Our app now generates this on ./gradlew jsNodeTest

```

Task :jsTestClasses

Task :compileTestDevelopmentExecutableKotlinJs

Task :jsTestDevelopmentGenerateLazyModules NO-SOURCE

Task :jsTestTestDevelopmentExecutableCompileSync

Task :jsNodeTest

Cleared command line test patterns to prevent Gradle validation


Exception during run: Error: Directory import '/home/mkienenb/IdeaProjects/gvea/performance-appraisal-frontend/build/js/node_modules/@mui/material/Box' is not supported resolving ES modules imported from /home/mkienenb/IdeaProjects/gvea/performance-appraisal-frontend/build/js/packages/performance-appraisal-frontend-test/kotlin/performance-appraisal-frontend.mjs
Did you mean to import "@mui/material/node/Box/index.js"?
at finalizeResolution (nodeinternal/modules/esm/resolve262:11)
at moduleResolve (nodeinternal/modules/esm/resolve864:10)
at defaultResolve (nodeinternal/modules/esm/resolve990:11)
at ModuleLoader.#cachedDefaultResolve (nodeinternal/modules/esm/loader755:20)
at ModuleLoader.resolve (nodeinternal/modules/esm/loader732:38)
at ModuleLoader.getModuleJobForImport (nodeinternal/modules/esm/loader317:38)
at ModuleJob.#link (nodeinternal/modules/esm/module job208:49) {
code: 'ERR_UNSUPPORTED_DIR_IMPORT',
url: 'file:///home/mkienenb/IdeaProjects/gvea/performance-appraisal-frontend/build/js/node_modules/@mui/material/Box'
}

Task :jsNodeTest FAILED

According to the LLM:

build/js/node_modules/@mui/material/package.json has no exports field at all.
Without exports, Node.js's ESM resolver has no subpath map to follow, so when Kotlin's generated .mjs tries to import @mui/material/Box, the ESM loader sees a directory with no guidance and throws ERR_UNSUPPORTED_DIR_IMPORT.

@turansky, I guess we need an example react project using MUI?