Just want to say, I really appreciate that the docs at http://cljs.github.io/api/ include the source code right at the bottom of each page. Makes finding the "ground truth" much easier and has gotten me way more comfortable with the language in general 🎉.

https://github.com/brandonbloom/fipp/issues/77#issuecomment-747850389

is this a bug?

How does one print an html entity with reagent again?

Nevermind, found the docs 😅

Good Morning Clojurians, I super confused. Why does shadow-cljs start the development http server when watching main build even if the :dev-http entry is in the :test build? Looking at the https://github.com/fulcrologic/fulcro-rad-demo/blob/master/shadow-cljs.edn, under :builds -> :test -> :devtools it calls for shadow-cljs back-end server to start. I have been assuming that it will only start for the test build, but when I start the main build, I still get the http server:

[I] /home/sporty/clojure/fulcro/fulcro-rad-demo-sittim~> shadow-cljs watch main
shadow-cljs - config: /home/sporty/clojure/fulcro/fulcro-rad-demo-sittim/shadow-cljs.edn
shadow-cljs - starting via "clojure"
shadow-cljs - HTTP server available at 
shadow-cljs - server version: 2.11.8 running at 
shadow-cljs - nREPL server started on port 9000
shadow-cljs - watching build :main
[:main] Configuring build.
[:main] Compiling ...
GUARDRAILS IS ENABLED. RUNTIME PERFORMANCE WILL BE AFFECTED.
Guardrails was enabled because the CLJS Compiler config enabled it
[:main] Build completed. (928 files, 0 compiled, 0 warnings, 18.48s)

@timofey.sitnikov dev-http is always started and not tied to any specific build in general. the new [dev-http](https://shadow-cljs.github.io/docs/UsersGuide.html#dev-http) docs make that a bit clearer. it can be useful to have that server to quickly test release builds and so on