This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-16
Channels
- # adventofcode (76)
- # aleph (1)
- # aws (2)
- # beginners (101)
- # boot (1)
- # boot-dev (1)
- # calva (25)
- # cider (12)
- # cljs-dev (29)
- # clojure (214)
- # clojure-europe (1)
- # clojure-nl (5)
- # clojure-spec (1)
- # clojure-uk (6)
- # clojurescript (155)
- # data-science (1)
- # datomic (48)
- # figwheel-main (5)
- # immutant (1)
- # leiningen (11)
- # nrepl (2)
- # off-topic (24)
- # pathom (2)
- # pedestal (2)
- # portkey (8)
- # protorepl (5)
- # re-frame (2)
- # rum (4)
- # shadow-cljs (21)
I'm trying to figure out how best to setup my library to be consumed by both shadow-cljs and vanilla cljs projects re: npm deps
Hmm. So if I need an alpha version of react, I'll probably have to get that onto cljsjs myself
for shadow-cljs it would be fine with deps.cljs
{:npm-deps {"react" "that-version"}}
unrelated question: you were doing some work on a UI for shadow-cljs. I remember seeing a REPL. was this a true, connected-to-my-app REPL?
actually just realized it’s in the current latest of shadow-cljs, answered my own question: it is! 😄
connecting to the nrepl server provided by shadow-cljs is an extra step we don't need 😉
I’m curious how it works then. I’m interested in embedding a CLJS REPL in an app for some dev tooling I’m thinking about… I was worried I would have to setup the self-hosted bootstrapping in any apps that used it tho