This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-09-24
Channels
- # 100-days-of-code (7)
- # announcements (1)
- # bangalore-clj (1)
- # beginners (87)
- # boot (6)
- # cljdoc (16)
- # cljsrn (13)
- # clojure (32)
- # clojure-dev (30)
- # clojure-italy (18)
- # clojure-nl (4)
- # clojure-serbia (1)
- # clojure-uk (48)
- # clojurescript (18)
- # cursive (18)
- # datascript (1)
- # datomic (7)
- # events (9)
- # figwheel-main (28)
- # fulcro (2)
- # hyperfiddle (2)
- # immutant (8)
- # jobs (16)
- # liberator (4)
- # nyc (2)
- # pedestal (15)
- # re-frame (8)
- # reagent (12)
- # reitit (8)
- # remote-jobs (1)
- # ring-swagger (2)
- # robots (1)
- # rum (1)
- # schema (1)
- # shadow-cljs (45)
- # spacemacs (49)
- # sql (13)
- # tools-deps (59)
- # uncomplicate (1)
- # vim (10)
Hi, what’s the relationship between fireplace, piggieback and figwheel? do I need to use all of them to do clojurescript dev using vim?
I’ve been fighting with this as well. fireplace is a vim plugin which can speak the nrepl protocol. Piggieback is a bridge between nrepl and clojure script. It seems to use dark magic. figwheel allows you to live edit your code and have the changes appear in the browser. Also uses the dark arts.
I only got it all working friday. But I can edit code in vim and have it reflect in chrome.
I’ve been working from this https://github.com/bhauman/figwheel-main/blob/master/docs/docs/vim.md
@markx @athomsonguy They are not really bound together. You can use figwheel without using a repl at all, it just hotreloads the code then. You can use piggieback without hot reloading. And you can use fireplace without even working with clojurescript. But to connect to clojurescript repl with fireplace, you do need to somehow upgrade the nrepl sessions from clj to cljs, and piggieback is one way (though not the only one).
@tomi.hukkalainen_slac So if I use figwheel without a repl, it will hotreload code when files are saved, right? And the repl is for eval code without saving the file? So do I still need repl when I have figwheel?
The figwheel repl will let interrogate the values on the page too. super useful for debugging user interaction.
@U63JKCFC3 I see. So it’s not only for eval.
Yes, figwheel will reload without a repl, just watghinc the files. Repl is for evaling, of course, but that has many uses. Trying out if something works, exploring a data structure, getting docs etc etc. Fireplace expects a repl for many of its functions, but that doesn't have to be a cljs repl, for most things plain clj will do as well. When using shadow, it will handle the parts that are normally done by figwheel and piggieback.
@markx @athomsonguy They are not really bound together. You can use figwheel without using a repl at all, it just hotreloads the code then. You can use piggieback without hot reloading. And you can use fireplace without even working with clojurescript. But to connect to clojurescript repl with fireplace, you do need to somehow upgrade the nrepl sessions from clj to cljs, and piggieback is one way (though not the only one).
@tomi.hukkalainen_slac So if I use figwheel without a repl, it will hotreload code when files are saved, right? And the repl is for eval code without saving the file? So do I still need repl when I have figwheel?
Yes, figwheel will reload without a repl, just watghinc the files. Repl is for evaling, of course, but that has many uses. Trying out if something works, exploring a data structure, getting docs etc etc. Fireplace expects a repl for many of its functions, but that doesn't have to be a cljs repl, for most things plain clj will do as well. When using shadow, it will handle the parts that are normally done by figwheel and piggieback.