Is there a way to def a variable in CLJS as the static result of a variable created in clj? Something like:

#?(:clj
   (def instance-types (read-aws-ec2-instance-types-from-file))
   :cljs (def instance-types ~instance-types))

This works but seems so painful. Is there a better way?

#?(:clj
   (defmacro def-instance-types
     [sym]
     (let [instance-types (read-aws-ec2-instance-types-from-file)]
       `(def ~sym ~instance-types))))

(def-instance-types instance-types)

@kenny Another approach would be to make use of goog-define, and arrange to have that value set based on the contents of the file at build time. This would limit you to using a primitive value but it also avoids statically baking the value into the JavaScript emitted by the compiler (and thus is compatible with the :aot-cache feature)

anybody have tips how to enable closure logging conditionally in production? I tried (goog.debug.Console/autoInstall) which doesn’t seem to suffice. Setting window.goog = {DEBUG: true} seems to break closure.

oh, I guess i can set goog.DEBUG after cljs_base and before my main…

@mkvlr setting that via :closure-defines doesn't work?

@dnolen I want to set it at runtime, not at compile time. To only enable logging when ?debug=1 is in the url.

I think Closure wants to elide all logging under advanced builds. Hrm.

yeah, that would be another problem but currently we’re just running with :simple

there’s this autoInstall functionality in closure: https://github.com/google/closure-library/blob/master/closure/goog/debug/console.js#L183

Ahh TIL. Cool!

but something else needs to happen for it to become active, trying if goog.debug.LogManager.initialize does the trick now…

Just setup a project using JUXT Edge but connecting to a repl produces: “Error building classpath. Manifest type not detected when finding deps for juxt.edge/app.logging in coordinate #:local{:root “../edge.app.logging”}”

the error is saying that it can't tell what kind of project this is (not seeing deps.edn or pom.xml - project.clj is not supported)

Yes, looking more closely I appear not to have cusstomised my deps.edn properly.

Thought specifying the name of the app when it was setup would have taken care of all that.

As a lein/project.clj user I find this way more confusing. Not good for inexperienced users.

Honestly getting a default setup to “just work” with 2 major Clojure frameworks today - Luminus and JUXT/Edge has proven futile.

Luminus borked on some reitit middleware even though I hadn’t selected it.

This JUXT config directory structure is so convoluted, I give up. I mean, what chance do new Clojurians have of making sense of all this. With lein there’s one config file - project.clj. Here you have an app structure which has to ../ to 16 folders all of which contain separeate deps.edn config files. I was attracted to Clojure for its simplicity, not this.

update your clj i believe

i think this relies on a fixed bug relating to locals/root that alex has already fixed

nested libspecs are not supported in CLJS?

(ns foo (:require [foo [bar]]))

(I personally don’t use them, just checking)

not supported

friends don't let friends use nested libspecs

and cljs is your friend

👍

I also love that CLJS doesn’t support use or refer-all