This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-28
Channels
- # aleph (48)
- # announcements (3)
- # bangalore-clj (1)
- # beginners (131)
- # cider (30)
- # cljdoc (6)
- # cljs-dev (53)
- # cljsrn (24)
- # clojure (312)
- # clojure-austin (2)
- # clojure-europe (4)
- # clojure-finland (6)
- # clojure-nl (24)
- # clojure-spec (24)
- # clojure-uk (66)
- # clojurescript (185)
- # core-async (46)
- # cursive (10)
- # data-science (9)
- # datomic (15)
- # devcards (2)
- # emacs (50)
- # fulcro (28)
- # jobs (1)
- # jobs-discuss (2)
- # kaocha (11)
- # lein-figwheel (12)
- # nyc (1)
- # off-topic (105)
- # other-languages (80)
- # pedestal (6)
- # re-frame (50)
- # reagent (5)
- # reitit (1)
- # remote-jobs (2)
- # ring (10)
- # rum (1)
- # shadow-cljs (10)
- # spacemacs (19)
I'm thinking about writing an in-browser ClojureScript REPL with some extra goodies (very focused on a specific task; essentially if *1 points to a specific kind of data, this data is displayed)
https://code.thheller.com/blog/shadow-cljs/2017/10/14/bootstrap-support.html I guess
did i see recently that :node-library
targets could be made single-file or am i imagining things?
closely related to this: https://github.com/thheller/shadow-cljs/issues/297. currently i deploy aws lambdas by copying and zipping all of node_modules
. cant tell if there was ever a final decision about allowing the source files to basically just be concatenated or if that introduced edge cases to the point of not being worthwhile
@nolan I worked on that a bit here https://github.com/thheller/shadow-cljs/issues/290 but I honestly don't recommend using it
you could use something like https://github.com/zeit/ncc that'll work a bit more reliable