[maxweber]

The problem

In a project depending on the compiler's artifact (cljf 0.12.12 and 0.12.13 from npm), a cold build whose cljs.core output comes from the per-user cache (cljs-core/, since 0.12.12) writes no goog-lib/ns/goog.math.Integer.js and no goog.Uri.js, the two Closure Library modules only cljs.core imports. The output then fails to load:

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '…/target/test/goog-lib/ns/goog.math.Integer.js' imported from …/target/test/cljs/core.js

Seen on every build after rm -rf target in a checkout that had built once before (the first build of a fresh checkout has no cache entry yet and compiles cljs.core, so it works; an incremental build keeps the modules of the build before). CLJF_CACHE_DIR=$(mktemp -d) or :core-cache false works around it.

The cause

cljf.esm/compile-ns loaded cljs.core's analysis through with-core-cljs when its output was up to date. That analyzes the classpath's cljs/core.cljs, the jar's entry, whose modification time differs from the analysis cache written for the copy in the output directory (by the compile of the output, or by restore-core!). requires-analysis? compares the two times, so the cache was judged stale and the source analyzed again, on every build, and the cache rewritten without :cljf.esm/goog-libs, which only compiling records (esm-goog-lib!). install-goog-libs then had cljs.core's modules only when something else used them too (goog.math.Long through transit, goog.string.StringBuffer).

In this repository's own tests cljs/core.cljs is a plain file, so the times matched and nothing showed.

The change

• compile-ns reads cljs.core's analysis from source-file's cache like every other namespace's (ana/analyze-file source-file), no with-core-cljs: the copy's time is the cache's. An up to date build no longer analyzes cljs.core's source either.
• esm_build_tests/restores-core-with-its-closure-libraries: cljs/core.cljs served from a jar through a child-first context class loader (it hides the parent's copy from check-classpath! too), cljf.main/cache-dir redefined to a directory of its own, two builds with the output deleted in between. Without the fix only its last assertions fail (the restored build lacks goog.math.Integer.js); with it the suite passes.
• A [Next] changelog entry under Fixed.

Checked

• script/test-esm: the build and REPL tests (40 tests, 219 assertions) and the runtime suite under Node 26 (670 tests, 21020 assertions), 0 failures, 0 errors.
• The build tests with the fix stashed: 29 tests, 1 failure, the new test.

The branch is on the storrito fork, as #7 was.

🤖 Generated with Claude Code

[k7d]

thanks!