I am using an npm module that has another npm dependency (Im not requiring this second one directly myself). In this transitory dep, the main entry in the package.json of this module does not properly export the names, but the module entry does. I would like to use this referred file in the build, but I'm wary of converting the entire build to :entry-keys ["module" "browser" "main"]. Is there a way to overide the entry key for one particular module? What is the best approach in a situation like this? Can I tell shadow somehow to use this specific entry point for that package?

$ shadow-cljs watch app

com/google/javascript/jscomp/CompilerOptions has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0

openjdk version "1.8.0_292"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_292-b10)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.292-b10, mixed mode)

it used to be java8 but is java11 these days

technically shadow-cljs would still be fine with java8, but the closure compiler started requiring java11 so we inherit that.

but I'd recommend upgrading to the latest java LTS release (17) directly

Thanks for the quick response

Every now and then, I encounter this error in our CLJS CI tests (in github actions):

File: /home/runner/work/nosco-gamma/nosco-gamma/cljs/nosco/ui/animations.cljs
invalid cljs source type
{:resource-id [:shadow.build.classpath/resource "nosco/ui/animations.cljs"], :resource-name "nosco/ui/animations.cljs", :source #object["[B" 0x27e3b83f "[B@27e3b83f"]}