I think you can do it like this :

(ns org.foo.macros
  (:require [cljs.env :as env]))

(defmacro m [x]
  (case (get-in  @env/*compiler* [:options :optimizations])
    :advanced `(js/console.log "In advanced")
    `(js/console.log "Not advanced")))

so basically use a macro, and at macroexpansion time emit different code

cool. does that also work for shadow?

yes, I was going for a macro

I only tested it on shadow he

could go with a goog-define?

this is more for a library than an app

it's not actually that important, but I think I could avoid some work in non-production builds

please allow the user to choose what to include or not, via properties example: guardrails https://github.com/fulcrologic/guardrails#clojurescript-considerations

there isn't one. CLJS doesn't have actual vars at runtime, so doing this does nothing useful.

Hmmm. I had gotten myself into a situation where I was using re-frame and reitit.frontend and had aliased :require [re-frame.core :as rf] and had decided to just refer in what I needed there and use the rf alias for reitit.frontend like their docs. Was not able to do so because of an alias error, just like I would get in Clojure. I had to work around that as it couldn't be rectified. Wasn't a big deal at all, true, but it would've been a little useful haha