With graal installed:
I'm leaning towards the second patch which disables implicit global imports. It's an ugly thing to rely on anyway ... for another ticket - but wondering if we should have `require` support for Java packages.
GraalVM ships with a bin/js and bin/nodejs binary, both use the GraalJS engine, but they default js.java-package-globals to true. So if one would use GraalVM's nodejs to run a ClojureScript artifact, they would still encounter issues regarding namespaces with one of the problematic prefixes. This of course is out of ClojureScript's control, but I thought it puts another perspective on the patch, as it doesn't cover all possible paths on how one can run into this issue.
Work has started to remove all usage of java-package-globals here:
CLJS-3087-2.patch conflicts with master, but perhaps we can close this ticket given the removal of the GraalJS REPL env
Yes, this can be closed.