This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-30
Channels
- # adventofcode (4)
- # aleph (1)
- # announcements (6)
- # babashka (11)
- # beginners (63)
- # calva (73)
- # clj-kondo (9)
- # clj-on-windows (20)
- # cljdoc (8)
- # cljsrn (4)
- # clojure (48)
- # clojure-europe (20)
- # clojure-italy (1)
- # clojure-nl (11)
- # clojure-spec (11)
- # clojure-uk (3)
- # clojurescript (32)
- # cloverage (1)
- # conjure (1)
- # cryogen (5)
- # datomic (83)
- # fulcro (28)
- # graphql (23)
- # gratitude (4)
- # helix (15)
- # honeysql (4)
- # improve-getting-started (14)
- # introduce-yourself (3)
- # jackdaw (5)
- # kaocha (11)
- # leiningen (1)
- # malli (1)
- # meander (5)
- # off-topic (18)
- # pathom (17)
- # pedestal (6)
- # polylith (15)
- # practicalli (1)
- # quil (2)
- # reitit (4)
- # releases (6)
- # shadow-cljs (38)
- # sql (20)
- # testing (6)
- # timbre (5)
- # tools-deps (11)
- # vim (2)
Morning. Ah the state of JS. Our frontend is written in JS. The build thing is yarn. So locally we use yarn to serve the frontend. The node process that does this (which admittedly also watches the files for rebuilds) takes 40% of my CPU. Basically doing nothing.
I’ve had the “pleasure” of changing the build-system of a somewhat large typescript project lately. Dealing with js/ts has become a nightmare tbh. I ended on using vitejs
and pnpm
. Had the project been all standard it would have been OK I guess, but with a little homegrown stuff there’s just a lot of feet and shotguns going around.
Don’t know if it’s still working for the frontend-devs, but at least now node is chugging along at 10% cpu.
if I’m correct, it was caused by missing globbing patterns in the ignore
thing of the watch options.
Morning!
Good morning 🙂
Morning!