This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-12-28
Channels
- # beginners (2)
- # calva (8)
- # capetown (1)
- # clojure (28)
- # clojure-europe (6)
- # clojure-norway (82)
- # clojure-sweden (1)
- # clojuredesign-podcast (5)
- # clojurescript (26)
- # core-async (3)
- # cryogen (7)
- # datahike (30)
- # datomic (10)
- # figwheel-main (8)
- # honeysql (8)
- # hyperfiddle (15)
- # jobs-discuss (6)
- # lsp (6)
- # matrix (6)
- # off-topic (12)
- # overtone (1)
- # polylith (6)
- # portal (6)
- # releases (1)
- # shadow-cljs (9)
- # sql (1)
- # xtdb (5)
Can anyone help? I’m building a library for use from within js node & browser apps as an ESM module. I’d also like to expose portal as a dev tool. However, I’m having issues compiling the ESM module with the portal.api ns. I think this is because shadow assumes a browser target. Thinking about it, something like the shadow remote path seems like a more suitable option as the concerns are better separated, but I feel like I’m going to get myself into the same place WRT compiling for node. Has anyone had any experience or have any hints regarding this?
I think I answered my own question. The web client uses js/fetch,
which works “everywhere”