I'm currently migrating to shadow-cljs (from using cljsbuild directly for prod, lein-figwheel for dev) and have some issues with promises that I handle through <p!. I require core.async like this:

[cljs.core.async :as async :refer [go >! <!]]
            [cljs.core.async.interop :refer [<p!]]

(let [p+ (.readFile ^js (.-promises ^js FS) dict-path)]
  (try (go (let [p (<!p p+)] ...))
       (catch default e (println e)))

TypeError: aa.setTimeout is not a function

hard to say. core.async does not require externs. what is the full stacktrace? not sure where setTimeout is used? and which build :target is this?

what’s the simplest way to compile some cljs snippet from the clojure repl? Or asked differently, could I call cljs.analyzer.api/emit and cljs.analyzer.api/analyze and with what state/env args so it knows symbols from my running shadow build?

compile or eval?

only compile

(I’ve used shadow.cljs.devtools.api/cljs-eval but I only want the js code, not the result)

best open is probably using the shadow.build api directly

https://github.com/thheller/shadow-cljs/blob/e53240007b45ab891f23edcb96b2ed377fafc471/src/repl/shadow/cljs/repl_test.clj#L188-L191

and https://github.com/thheller/shadow-cljs/blob/e53240007b45ab891f23edcb96b2ed377fafc471/src/repl/shadow/cljs/repl_test.clj#L11-L32

after that there is a :repl-state key in the build state, which contains a bunch of :repl-actions

basically all of those need to happen before the last repl/process-input can be eval'd

but its all just compiled, no eval JS env required

very low level though

can I also use the running shadow watch and compile a string as if came in the end of my file?

but there aren't many repl-actions and they are sort of self explanatory

no

I mean in theory yes, but none of the targets have the necessary hooks or functionality to do that

and there’s no cljs.analyzer.api/analyze compatible state/env available either with shadow, is that right?

well the context matters here

you cannot just mess with a watch and expect it to work

watch after all manages a build-state in a very specific way

if you just take it out and mess with it there is no way to "put it back"

but yes, you can take it out and mess with it

so for Clerk’s render functions are currently quoted form that are evaluated through sci

like https://github.com/nextjournal/clerk/blob/626ea1e8c07359c3996d63cfd5fff6e34dc0989b/src/nextjournal/clerk/viewer.cljc#L703 or sometimes just symbols like https://github.com/nextjournal/clerk/blob/626ea1e8c07359c3996d63cfd5fff6e34dc0989b/src/nextjournal/clerk/viewer.cljc#L714

now trying to figure out if I can alternatively support proper compiled cljs

which means I need to compile some of those quoted forms…

well you can do anything with the shadow.build api, its just not documented much

@mkvlr if the quoted form is known at compile time, why do you even quote it and not just compile it as regular cljs?

@borkdude that’s all I’m trying to do in a first step

seems like that's a recurring problem, but.. trying to use @openfin/excel - and getting the following problem:

WARN:
shadow-cljs - failed to load module$node_modules$$openfin$excel$openfin_excel
shadow.js.jsRequire @ js.js:74
shadow.js.require @ js.js:113
eval @ app.excel.js:2
goog.globalEval @ main.js:566
env.evalLoad @ main.js:1659
(anonymous) @ main.js:2574

main.js:1661 An error occurred when loading app.excel.js
env.evalLoad @ main.js:1661
(anonymous) @ main.js:2574

ReferenceError: fin is not defined
    at shadow$provide.module$node_modules$$openfin$excel$openfin_excel (:3900/js/cljs-runtime/module$node_modules$$openfin$excel$openfin_excel.js:17:34)
    at shadow.js.jsRequire (:3900/js/cljs-runtime/shadow.js.js:34:18)
    at shadow.js.require (:3900/js/cljs-runtime/shadow.js.js:59:20)
    at eval (:3900/js/cljs-runtime/app.excel.js:2:64)
    at eval (<anonymous>)
    at goog.globalEval (main.js:566:21)
    at env.evalLoad (main.js:1659:12)
    at main.js:2574:12

sorry never used that lib. don't know what fin is supposed to be. looks to be expecting to be running in excel? but looks like you are running this in a browser?

I have a question about avoiding these kind of errors: throw new Error('Namespace "' + name + '" already declared.'); I'm basically trying to use ViteJS and ShadowCLJS together but the hot reloading of Vite wants to recall goog.provide for everything when my ShadowCLJS ESM modules changes. I found an https://github.com/minimal-xyz/minimal-shadow-cljs-webpack/blob/master/lib/page.js#L1-L5 that might workaround the issue, but I wanted to check with anyone if that seems correct, or if there is a better way to avoid calling all of the goog.provide functions again. Thanks in advance 🙏

Hey there, I have two builds, each with an http dev server defined. But they both appear to launch, even when I'm only launching one build:

{:test {:target   :browser-test
        ...
        :devtools {:http-port 8021 ...}}
 :dev  {:target   :browser
        ...
        :devtools {:http-port 8022 ...}}}

$ clojure -M:cljs/dev:cljs/client watch dev
shadow-cljs - HTTP server available at 
shadow-cljs - HTTP server available at 
shadow-cljs - server version: 2.20.2 running at 
shadow-cljs - nREPL server started on port 60050
shadow-cljs - watching build :dev
[:dev] Configuring build.
[:dev] Compiling ...
[:dev] Build completed. (512 files, 0 compiled, 0 warnings, 4.21s)

http servers are not build related and the config in the build config has been deprecated for 5+ years now. use https://shadow-cljs.github.io/docs/UsersGuide.html#dev-http instead

they are meant to always run, so you can use them for release or compile builds as well as watch