This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-12
Channels
- # announcements (4)
- # asami (3)
- # babashka (18)
- # babashka-sci-dev (2)
- # beginners (55)
- # calva (18)
- # clj-commons (23)
- # clj-kondo (2)
- # cljfx (7)
- # cljs-dev (15)
- # clojure (96)
- # clojure-europe (43)
- # clojure-losangeles (3)
- # clojure-nl (2)
- # clojure-uk (11)
- # clojurescript (1)
- # datalevin (2)
- # datomic (10)
- # events (1)
- # google-cloud (4)
- # gratitude (16)
- # helix (3)
- # hyperfiddle (63)
- # inf-clojure (13)
- # introduce-yourself (4)
- # ipfs (2)
- # jobs (2)
- # jobs-discuss (12)
- # leiningen (7)
- # lsp (15)
- # off-topic (38)
- # polylith (24)
- # portal (27)
- # remote-jobs (8)
- # sci (27)
- # spacemacs (5)
- # specter (1)
- # sql (5)
- # xtdb (41)
hello there! I'm new here
are there examples of setting up a polylith-like project with shadow-cljs?
what about using just the core idea?
like, composable packages
did any one tried that with cljs?
or shadow-cljs
great!
The tools won’t support it, but the tool is really just a nice to have for the concept.
I'll try by myself and see where I can get
what are you trying to achieve? Code sharing between multiple frontends? I think there's easier ways to do that
not really
my use case is very specific and not actually frontend
more like nodejs
I see, silly of me to immediately assume cljs = frontend 🙂
We're slowly porting our project to polylith and we use shadow-cljs. Currently we have all frontend related code in the project folder. We also run app from the project folder, so it's the working directory for most of our scripts related to the app, and contains all the compiled frontend files too.