This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-16
Channels
- # announcements (8)
- # aws (28)
- # babashka (26)
- # beginners (125)
- # calva (18)
- # chlorine-clover (2)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (4)
- # clojure (134)
- # clojure-europe (31)
- # clojure-italy (2)
- # clojure-nl (14)
- # clojure-uk (83)
- # clojurescript (81)
- # conjure (4)
- # cursive (2)
- # datomic (145)
- # emacs (13)
- # events (3)
- # figwheel-main (14)
- # fulcro (30)
- # graalvm (23)
- # graphql (15)
- # helix (21)
- # jackdaw (20)
- # juxt (1)
- # lambdaisland (4)
- # leiningen (2)
- # malli (12)
- # meander (22)
- # observability (22)
- # off-topic (27)
- # pedestal (3)
- # re-frame (12)
- # reitit (1)
- # releases (2)
- # rewrite-clj (3)
- # shadow-cljs (67)
- # spacemacs (7)
- # sql (1)
- # tools-deps (19)
- # unrepl (2)
- # xtdb (25)
Anyone else using re-frame-10x with the new webpack? If you use :exclusions [cljsjs/react-highlight]
so that :npm-deps true
works it doesn’t take that well… It seems to work without using the exclusions, but I’m not 100% certain that’s a good thing…
I added a :clean-outputs
Figwheel option and a --clean
CLI opt to the 0.2.9 release of figwheel.main
this may not solve your problem with re-frame-10x as it depends on how they refer to the react-highlight library
This may not be right https://github.com/day8/re-frame-10x/blob/master/src/day8/re_frame_10x/view/components.cljs#L11
yep that’s a problem the global-export name is react-highlight.js and not react-highlight
yeah my doc’s have little to do with this problem, but they are the result of the problems you had when you tried to get advanced compile working
@juhoteperi ^ refering to above shouldn’t react-highlight also be exported as react-highlight
so that npm dependency resolution works correctly?
The npm name is react-highlight.js
so the package should be correct