This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-11-24
Channels
- # adventofcode (4)
- # announcements (1)
- # aws (6)
- # babashka (18)
- # babashka-sci-dev (18)
- # beginners (12)
- # calva (43)
- # circleci (3)
- # clj-kondo (96)
- # cljdoc (2)
- # clojure (89)
- # clojure-australia (2)
- # clojure-europe (26)
- # clojure-nl (3)
- # clojure-norway (11)
- # clojure-spec (8)
- # clojure-uk (1)
- # clojurescript (28)
- # cursive (25)
- # datahike (6)
- # datalevin (56)
- # datomic (12)
- # docker (15)
- # emacs (9)
- # events (2)
- # figwheel (3)
- # fulcro (15)
- # gratitude (10)
- # introduce-yourself (8)
- # lsp (16)
- # malli (6)
- # nbb (2)
- # off-topic (23)
- # other-languages (2)
- # pathom (4)
- # portal (25)
- # practicalli (1)
- # re-frame (9)
- # releases (1)
- # shadow-cljs (8)
- # sql (6)
- # timbre (3)
I can't seem to get any debug tools working with my Clojurescript setup. I've tried Portal and Flowstorm. I could use some help.
Hello, some keywords evaluate to null
when I call name
on them, anyone knows why?
I don't know if I'm doing something wrong, but the compilation times are unacceptable, incremental compilation definitely doesn't work, and to top it off, postcss can get into a infinite loop and crash because it runs out of memory
currently there is nothing there, so no problem, but in general it would be useful to be able to modify the theme
can’t seem to find it, maybe @U45J3R52L who did the work still knows what do search for?
https://github.com/nextjournal/tailwindcss/commit/3241dc201c37fc718d0c7c4989fd6c58e50b0cf6
but fwiw we’re much happier with the play cdn in dev now, one process less to care about
I find more and more often I end up ditching internal file watchers and just leaning on a more general purpose shell thing like entr
(http://eradman.com/entrproject/).
so instead of npx tailwindcss ,,, --watch
it's find target/cljs-out/**/*.js | entr npx tailwindcss ,,,
(without the watch). Since tailwind went jit-by-default I don't find there's a lot of benefit to dev mode so I just run with minified production builds all the time.
There's probably a way to pair it with a debouncing trick like https://github.com/MerkleBros/debounce.sh/blob/master/debounce.sh, so it only kicks in every 2-5s on the hot reload.
Not sure what the etiquette is of bringing back old threads from the dead but I've been encountering this same problem (tailwindcss watch workflow is buggy, slow, and occasionally crashing on an OOM error) and am wondering if you can elaborate more on your solutions. My tailwind setup basically follows this repo: https://github.com/jacekschae/shadow-cljs-tailwindcss but I am not sure how to go from there to the cdn solution in that view.clj
file or this debouncing/entr method.
Not sure what the etiquette is of bringing back old threads from the dead but I've been encountering this same problem (tailwindcss watch workflow is buggy, slow, and occasionally crashing on an OOM error) and am wondering if you can elaborate more on your solutions. My tailwind setup basically follows this repo: https://github.com/jacekschae/shadow-cljs-tailwindcss but I am not sure how to go from there to the cdn solution in that view.clj
file or this debouncing/entr method.