This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-30
Channels
- # announcements (5)
- # babashka (5)
- # beginners (39)
- # calva (1)
- # chlorine-clover (22)
- # circleci (4)
- # clara (5)
- # clj-kondo (1)
- # cljs-dev (2)
- # cljsrn (8)
- # clojure (46)
- # clojure-canada (15)
- # clojure-norway (3)
- # clojure-uk (6)
- # clojurescript (39)
- # conjure (10)
- # core-async (9)
- # datomic (2)
- # figwheel-main (26)
- # fulcro (33)
- # ghostwheel (9)
- # jobs (6)
- # leiningen (1)
- # malli (7)
- # music (1)
- # off-topic (48)
- # re-frame (11)
- # reagent (1)
- # shadow-cljs (86)
- # spacemacs (8)
@folcon with the bundle target the bundler cant process the output-to if its not in output-dir
Has someone tried figwheel-main 0.2.6 with vim-fireplace? I can connect with Piggieback but when trying to evaluate I'm getting Not supported: class figwheel.repl.FigwheelReplEnv$fn__16105
.
I'm also seeing this previously fixed problem reappear: https://github.com/bhauman/figwheel-main/issues/145
I tried both the older clojurescript 1.10.597 and 1.10.773 with figwheel-main 0.2.6, in both cases the issue #145 seems to be present
0.2.7-SNAPSHOT also has :bundle-freq
which can either be :once
, :always
or :smart
which checks for changes to output-to or npm_deps.js
I’d love to deploy 0.2.7 tomorrow as its the end of month 1 of the Clojurists Together Quarter
Evaluations are showing #object[cider.piggieback.UnknownTaggedLiteral ...]
when returning eg. atom or a function, normally there should be eg.`#object[clojure.lang.Atom ...]`, but I guess that might not be a problem in figwheel-main
Never mind, found that documented in Piggieback: https://github.com/nrepl/piggieback/blob/master/README.md#pretty-printing