This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-30
Channels
- # aws (1)
- # bangalore-clj (1)
- # beginners (73)
- # boot (13)
- # cider (3)
- # clara (19)
- # cljs-dev (33)
- # cljsrn (37)
- # clojure (177)
- # clojure-dev (13)
- # clojure-gamedev (1)
- # clojure-italy (10)
- # clojure-nlp (1)
- # clojure-russia (1)
- # clojure-spec (64)
- # clojure-uk (128)
- # clojurescript (177)
- # core-async (23)
- # cursive (5)
- # datascript (13)
- # datomic (20)
- # devops (49)
- # emacs (13)
- # graphql (5)
- # hoplon (13)
- # keechma (1)
- # leiningen (3)
- # liberator (4)
- # lumo (2)
- # off-topic (11)
- # om (19)
- # om-next (3)
- # onyx (6)
- # re-frame (13)
- # reagent (14)
- # ring-swagger (7)
- # rum (2)
- # spacemacs (7)
- # unrepl (1)
- # untangled (23)
- # vim (8)
- # yada (1)
anyone used react-native-video? I need to stream a video from my backend with http request..
@domkm are you seeing any problems?
@pesterhazy: Yes, I think it's related to the switch to using create-react-class.
what's the error message?
did you add the additional npm dependency create-react-class?
I haven't tried yet
Hi! I’m currently using expo app and clojurescript and I’m having trouble getting my tests to run. Anyone else getting tests to work using straight-up react-native or re-natal? (ie, is it just an expo problem?)
I get #object[TypeError TypeError: undefined is not an object when trying to run a test (or even do a #macroexpand)
I tried to upgrade my well-working re-natal setup from RN 0.44.2 to RN0.45 but it seems that the memory issues when running the packager are back
Others have stumbled on that issue it seems: https://stackoverflow.com/questions/44527754/react-native-javascript-heap-out-of-memory-no-fix-worked
I’m on node v7.8, I’ll try upgrading to v8.1.3 since there are a few enhancement to memory since v8.0 and see if that changes anything
@gphilipp what I do is to use "dev" mode, i.e. not use whole-program optimization
haven't tried with recent version of RN though
@pesterhazy dev mode ? When using the packager ?
@pesterhazy oh I get it, in the node line right ? --dev false
-> --dev true
?
the drawback is that it sets DEV__ to true as well (in the js file)
so you need to go in and change it to false (so you don't see yellow boxes/red boxes and slow perf)
or write a script that changes the flag
@mfm (def multi-slider (r/adapt-react-class (.-default (js/require "@ptomasroos/react-native-multi-slider"))))
you don’t say. i’ll try that now. thanks. i wish i could ask a more intelligent question than: why do i have to include (.-default...
? is it an idiosyncrasy of react-native-multi-slider
? a bug in adapt-react-class
? i’ve not ever seen ...(.-default...
in example reagent projects, though i haven’t looked hard.
@pesterhazy I see, thanks for the heads up, for the record I’ve filed a gist https://gist.github.com/gphilipp/6712452b2c7d5151b5d93c0417f48e15
@mfm the reason is this: https://github.com/ptomasroos/react-native-multi-slider/blob/master/MultiSlider.js#L15
Oddly, requiring core.async
(and its macros) appears to be causing my Xcode build to get stuck for a long time (5 minutes or so) at the “Running 1 of 1 custom shell scripts” phase for a release build, and then fail. I don’t know if it is something about the resulting JavaScript, or if it is simply some size threshold (the JavasScript only goes from 2.3 to 2.4 MB). This is a re-natal
based app, after doing lein prod-build
with pretty much the stock settings (`:optimizations :simple`, etc.)