Hello everyone, coming from the Apache Solr proje...

# compose-web

[Christos Malliaridis]

Hello everyone,

coming from the Apache Solr project, we have recently added an experimental module with Compose for the Admin dashboard (with jvm and wasm targets).

In some builds (noticeably with JDK >21), we are facing a NPE for the optimizeTask in our jenkins jobs when binaries.executable() is called, and we can't reproduce the issue locally to troubleshoot and fix it. The console output can be found here. The gradle configuration of the module can be found here.

Does anyone have any clue what the cause could be or how to reproduce or address the issue?

[Alex Styl]

is node version the same in both environments?

[Christos Malliaridis]

It should be, yes. I tried different versions of node and also with no node js installed, as it seems that compose-web is installing it automatically and using that instead?

It may be worth mentioning that we also use com.github.node-gradle.node in another module in the project, that installs node 16 (aside from the node used by compose probably), and that we also had some compatibility issues before related to OS, see https://youtrack.jetbrains.com/issue/KT-58502, which we considered downgrading node for compose to v16.

But none of these cause any issues in local environments, which does make the reproduction of the issue harder. Perhaps its an OS (version) specific issue?

[Christos Malliaridis]

The error turned out to be caused by alternative JDKs being used during the builds. Not directly related to compose-web. 🙂