shadow.build.cljs-bridge — thheller/shadow-cljs 2.3.32

things that connect the shadow.cljs world with the cljs world

*in-compiler-env* clj

ana-is-cljs-def? clj

(ana-is-cljs-def? fqn)

(ana-is-cljs-def? ns sym)

checked whether a symbol in a given namespace is defined in CLJS (not a macro)

check-renames! clj

(check-renames! {:keys [renames rename-macros] :as ns-info})

check-uses! clj

(check-uses! {:keys [env uses use-macros] :as ns-info})

ensure-compiler-env clj

(ensure-compiler-env state)

error clj

(error env error-type error-data)

get-build-state clj

(get-build-state)

get-resource-info clj

(get-resource-info resource-name content reader-features)

nested-vals clj

(nested-vals map)

register-goog-names clj

(register-goog-names state)

register-ns-aliases clj

(register-ns-aliases {:keys [ns-aliases str->sym] :as state})

registers all resolved ns-aliases with the CLJS compiler env so it doesn't complain

swap-compiler-env! clj

(swap-compiler-env! state update-fn & args)

with-compiler-env clj/s macro

(with-compiler-env state & body)

compiler env is a rather big piece of dynamic state so we take it out when needed and put the updated version back when done doesn't carry the atom arround cause the compiler state itself should be persistent thus it should provide safe points

the body should yield the updated compiler state and not touch the compiler env