This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-28
Channels
- # ai (1)
- # beginners (239)
- # bitcoin (1)
- # boot (4)
- # cider (5)
- # clara (3)
- # cljs-dev (16)
- # cljsjs (5)
- # cljsrn (1)
- # clojure (152)
- # clojure-android (3)
- # clojure-dev (3)
- # clojure-greece (4)
- # clojure-italy (5)
- # clojure-spec (14)
- # clojure-uk (24)
- # clojurescript (81)
- # data-science (1)
- # datomic (47)
- # devcards (34)
- # docs (3)
- # emacs (6)
- # ethereum (1)
- # events (9)
- # flambo (5)
- # fulcro (11)
- # graphql (1)
- # immutant (3)
- # lein-figwheel (2)
- # leiningen (2)
- # luminus (6)
- # lumo (90)
- # off-topic (25)
- # proton (2)
- # re-frame (44)
- # reagent (5)
- # ring (7)
- # ring-swagger (11)
- # shadow-cljs (11)
- # spacemacs (6)
- # vim (13)
- # yada (25)
https://www.reddit.com/r/Clojure/comments/72wf86/shadowcljs_js_dependencies_going_forward/
just wanted to chime in and say I’ve been using shadow-cljs happily for a few days
just been using a basic watch
and repl
setup for a web app
errors are good, and warnings survive across file saves
one thing I noticed is that ctrl+c
exits the repl instead of exiting the current command, and running it with rlwrap
doesn’t allow up-arrow to recall commands from previous session
regarding externs, I’ve decided to avoid the problem and just use cljs-oops for all js-related interop
@shaunlebron I don’t think ctrl+c
can work in a CLJS environment, there is nothing like Thread.interrupt
in JS. not sure how to make history work.