This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-06-17
Channels
- # announcements (2)
- # aws (4)
- # babashka (20)
- # beginners (256)
- # calva (15)
- # chlorine-clover (1)
- # cider (12)
- # clj-kondo (25)
- # cljsrn (16)
- # clojure (115)
- # clojure-europe (7)
- # clojure-finland (5)
- # clojure-italy (10)
- # clojure-nl (35)
- # clojure-spec (13)
- # clojure-uk (83)
- # clojurescript (42)
- # code-reviews (81)
- # conjure (8)
- # cursive (6)
- # data-science (1)
- # datomic (3)
- # duct (18)
- # emacs (2)
- # figwheel-main (40)
- # fulcro (21)
- # helix (1)
- # jackdaw (7)
- # java (2)
- # lein-figwheel (5)
- # luminus (1)
- # observability (12)
- # off-topic (32)
- # parinfer (5)
- # pedestal (19)
- # re-frame (5)
- # reagent (8)
- # reitit (17)
- # rewrite-clj (47)
- # rum (19)
- # shadow-cljs (48)
- # spacemacs (4)
- # sql (40)
- # tools-deps (22)
- # vrac (1)
- # xtdb (25)
@juhoteperi thanks 🙂
I thought we weren’t supposed to use this style of import?
["react-highlight.js" :as react-highlightjs]
Also been thinking about looking at react-native specifically the microsoft stuff, would that be a good stress test of the new figwheel-main webpack?This is super confusing, as this exists too:
(https://www.npmjs.com/package/react-highlight)
I’m not importing anything specifically, just used :npm-deps true
I just looked at lein deps :tree
and excluded the cljsjs/react-highlight
dep because I remembered that happened the last time…
Yep, I stopped when it broke, but I thought I’d report it just in case it was a symptom of an underlying issue, I mean in this case it’s ok it’s not a prod dep, but it could easily have been =)…
Would that work with this: https://microsoft.github.io/react-native-windows/ The main targets I care about are OS’s not mobiles…
react-native-figwheel-bridge doesn’t currently let you require images/pngs etc in the clojurescript codebase
Loving what’s happening with the tooling btw, it’s great to see all the stuff that’s been added in!
I’ve got a windows machine and a macos, I primarily dev in macos, but I can test against both…
@folcon that’s cool, do you mind if I hit you up for some testing on windows sometime?
No problem =)… Happy to help as and when I have time, just drop me a message and I’ll respond when I can 😉
but also the new SSL stuff would be nice to get my certifiable library working on windows
My pet project is doing some gamedev, so making sure this stuff just works with media is something I really want to see =)…
cool well the work is scheduled to start in a couple of weeks to get react-native integrated including support for images
Btw, this is the error if I do [day8.re-frame/re-frame-10x "0.6.5" :exclusions [cljsjs/react-highlight]]
:
[Figwheel] Failed to compile build dev in 145.833 seconds.
[Figwheel:WARNING] Compile Exception resources/public/js/compiled/out/day8/re_frame_10x/view/components.cljs line:11 column:15
No such namespace: react-highlight.js, could not locate react_highlight/js.cljs, react_highlight/js.cljc, or JavaScript source providing "react-highlight.js" (Please check that namespaces with dashes use underscores in the ClojureScript file name) in file resources/public/js/compiled/out/day8/re_frame_10x/view/components.cljs
Which reminds me I was performing clean manually in my run script, now need to see if I can just call the figwheel's clean
…
With regards to caching at the moment I delete all of my node_modules as well as my complied code before running npm install
and then compiling from scratch.
I absolutely want to ensure reproducible builds while this is being worked on.
Not sure where else this could be caching unless I’ve gotten everything?