This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-17
Channels
- # aleph (3)
- # bangalore-clj (2)
- # beginners (76)
- # boot (37)
- # braid-chat (7)
- # business (1)
- # clara (1)
- # cljsrn (45)
- # clojure (36)
- # clojure-android (1)
- # clojure-austin (2)
- # clojure-dusseldorf (4)
- # clojure-spec (2)
- # clojure-uk (2)
- # clojurebridge-ams (4)
- # clojurescript (79)
- # clr (1)
- # community-development (5)
- # core-async (1)
- # cursive (4)
- # data-science (1)
- # funcool (3)
- # hoplon (3)
- # om (107)
- # om-next (6)
- # other-lisps (1)
- # overtone (1)
- # planck (2)
- # reagent (24)
- # rum (1)
- # specter (7)
- # yada (46)
is that just me or boot-reload is as good as figwheel?
Figwheel has a few more features but the basics should be similar @yury.solovyov
styles and code reload are enough for me atm
@yury.solovyov there are some quirks to it
e.g. Figwheel has very nice integration with CIDER, boot-reload is still a bit lacking in that sense
another thing: Figwheel can “see” your CLJS namespaces and you can require them at the REPL
for boot-reload you need to add them explicitly under :requires
in your .cljs.edn
@anmonteiro not sure how REPL and :requires
interplay but I think Figwheels REPL stuff is just a separate task in boot: boot-cljs-repl
What more does Figwheel do in that regard?
@martinklepsch oh right, I’m conflating things
I meant the connection between boot-reload
and boot-cljs-repl
I have no idea how Figwheel works in that sense though
but I was too used to it working out-of-the-box™
I’ve been slowly learning how to do what I want in Boot
Boot-cljs stack doesn't currently set the directories for REPL correctly I think
^ this might be the problem
It should use the same cache-dir as compiler but there were complications on implementing that
https://github.com/adzerk-oss/boot-cljs-repl/compare/repl-output-dir this was my latest attempt
Figwheel also has it's own REPL implementation while Boot-cljs-repl uses Weasel
@juhoteperi is this problem also related to me seeing a stray “out” dir sometimes at the root of my project?
gotcha
IIRC that branch should have fixed it, but for some reason didn't work
I’m using clj-v8
as a lib, and trying to boot test
. I’m getting: Caused by java.lang.UnsatisfiedLinkError Native Library /private/var/folders/gb/44z6jbb93f71d5npbyqzk5lh0000gn/T/libv8.dylib.clj-v8 already loaded in another classloader
is there a way to make a pod start from the current classloader? Seems like clj-v8
breaks every single use of pods
the problem is that these libraries don't check to see if a native lib is already loaded before they try to load it
specifically this answer: https://github.com/boot-clj/boot/issues/484#issuecomment-236681493
ah, yep, there’s an open PR for clj-v8: https://github.com/circleci/clj-v8/pull/15