Fork me on GitHub

Does anyone have any idea why I'd be getting a circular deps error on my second build? (The first one is fine).


[email protected] ~/src/interactive-syntax (main*) $ clojure -A:package
2020-11-29 00:36:21.164:INFO::main: Logging initialized @3122ms to org.eclipse.jetty.util.log.StdErrLog
[Figwheel] Compiling build prod to "target/public/cljs-out/prod/main.js"
Nov 29, 2020 12:36:58 AM println
WARNING: /home/leif/src/interactive-syntax/target/public/cljs-out/prod/cljs/compiler.js:860: WARNING - [JSC_REGEXP_REFERENCE] References to the global RegExp object prevents optimization of regular expressions.
cljs.compiler.emit_constant_STAR_.cljs$core$IMultiFn$_add_method$arity$3(null,RegExp,(function (x){

Nov 29, 2020 12:36:58 AM println
WARNING: /home/leif/src/interactive-syntax/target/public/cljs-out/prod/interactive_syntax/core.js:47: WARNING - [JSC_PARTIAL_NAMESPACE] Partial alias created for namespace cljs, possibly due to await/yield transpilation.
This may prevent optimization of anything nested under this namespace.
See  for more details.
(runner.g = ({"cljs": cljs}));

Nov 29, 2020 12:36:58 AM printSummary
WARNING: 0 error(s), 2 warning(s)
[Figwheel] Successfully compiled build prod to "target/public/cljs-out/prod/main.js" in 35.165 seconds.
[Figwheel] Bundling: npx webpack --mode=production src/js/bundle.js ./target/public/cljs-out/prod/main.js --output-path ./target/public/cljs-out/prod --output-filename main_bundle.js
[email protected] ~/src/interactive-syntax (main*) $ clojure -A:package
2020-11-29 00:41:26.361:INFO::main: Logging initialized @3092ms to org.eclipse.jetty.util.log.StdErrLog
[Figwheel] Compiling build prod to "target/public/cljs-out/prod/main.js"
[Figwheel] Failed to compile build prod in 10.046 seconds.
[Figwheel:WARNING] Could not Analyze: Assert failed: Circular dependency detected, cljs.core -> cljs.core
(every? (fn* [p1__2127#] (not (contains? *cljs-dep-set* p1__2127#))) deps)  target/public/cljs-out/prod/cljs/core.cljc   
[Figwheel:SEVERE] failed compiling file:target/public/cljs-out/prod/cljs/core.cljc
Unexpected error (AssertionError) compiling at (REPL:1).
Assert failed: Circular dependency detected, cljs.core -> cljs.core
(every? (fn* [p1__2127#] (not (contains? *cljs-dep-set* p1__2127#))) deps)

Full report at:


The command I'm running is clojure -m figwheel.main --build-once --prod


With the following deps:

{:deps {org.clojure/core.match {:mvn/version "1.0.0"}
        org.clojure/tools.reader {:mvn/version "1.3.3"}
        reagent {:mvn/version "0.10.0" :exclusions [cljsjs/react cljsjs/react-dom]}
        alandipert/storage-atom {:mvn/version "1.2.4"}
        com.bhauman/figwheel-main {:mvn/version "0.2.12"}
        com.bhauman/rebel-readline-cljs {:mvn/version "0.1.4"}}
 :paths ["src" "target" "resources" "env/dev/cljs" "env/prod/cljs"]}}


Do not include "target" in your :paths.


@p-himik Ah, okay. FWIW, the figwheel-main tutorial ( does put target in the paths. Is that wrong, or is there a different reason they do that?


No idea why they do it but I fail to see how it would be the right thing to do.


> This directory is automatically added to the > classpath so that the compiled assets can be found and served by the > built-in webserver. Well, if they're mixing the classpath for building CLJS and the classpass for serving compiled files then it's certainly wrong.


I see...that actually makes more sense.


(I was left not really understanding what the classpath is used for after reading that tutorial)


Hi guys, I'm trying to do an advanced compile and deployment of my webapp into an ec2 instance ... I am getting ...

[email protected]2-31-71-196:~/dbfrontend-clone/src/dbfrontend$ lein do clean, cljsbuild once min
*** Warning: This project requires Leiningen 2.9.1, but you have 2.8.1 ***

Get the latest version of Leiningen at  or by executing
"lein upgrade".
Compiling ClojureScript...
Compiling ["resources/public/js/compiled/dbfrontend.js"] from ["src"]...
    throw err;

Error: Cannot find module '@cljs-oss/module-deps'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at [eval]:8:13
    at ContextifyScript.Script.runInThisContext (vm.js:50:33)
    at Object.runInThisContext (vm.js:139:38)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:652:30)
    at evalScript (bootstrap_node.js:463:27)

Successfully compiled ["resources/public/js/compiled/dbfrontend.js"] in 25.769 seconds.


Is there any issue i should be fixing? Otherwise how do I start my app?


This is my repo btw Not sure if there's issues with project.clj


I would try upgrading leiningen first:


Is there a way to change the dependency for lein instead?


you can see your installed version with: $ lein version


@p-himik Looking at the clojure docs here:, it seems it would indicate adding traget to the classpath is the right thing to do, is this a difference between clojure and clojurescript?


Yes. In Clojure, compiled files take precedence over older sources - they completely replace them. In ClojureScript, there's no such thing (unless we're talking about only CLJS files, but target also has JS files) - all files are added together. Even if it was possible, it would still be detrimental - your CLJS compilation process has absolutely nothing to do with your backend operations. So it doesn't make any sense to pollute the backend classpath with the stuff from the CLJS compilation classpath that, apart from just the sources, can have some third-party dependencies that bring in yet other dependencies.


Ah, okay. This makes sense.


Thank you.

👍 3

@p-himik Hmm...I still am getting circular dependency errors, even after a clean rebuild. Any other ideas?


Does the error say anything about the particular set of dependencies?


Oh, wait - the docs said that "target" is implicitly added to the paths by Figwheel, I think.


If that's indeed the case then it might be better to ask it in #figwheel - I've switched over to shadow-cljs a few years ago.


@p-himik Ugg...I missed that. Thanks for catching it.


And ya, I'll jump into figwheel.


@p-himik So, when I last looked at shadow-cljs, it seemed to include npm packages directly. Does that mean you can't use webpack with shadow-cljs?


I've never used Webpack but it seems like it's possible: