Fork me on GitHub
#cljsrn
<
2017-07-20
>
sekao00:07:38

not confidence inspiring šŸ˜…

zlrth00:07:24

iā€™m able to npm install use-component and js/require it. iā€™m using re-natal 0.5.0, npm 4.6.1,

jeaye00:07:22

We're on re-natal 0.4.0 (released May 1st), so my advice is based on that.

jeaye00:07:46

Sounds like things are less clunky in 0.5.0, if you're able to upgrade to it. šŸ™‚

sekao00:07:52

i am on re-natal 0.5.0 and npm 5.0.3

zlrth00:07:33

i was flummoxed for a bit. i removed react-navigation from my project, rebuilt, and was getting unknown named module: 'react-navigation'. but then i saw that i didnā€™t remove (js/require "react-navigation") from my code.

zlrth00:07:21

so, ā€œunknown named moduleā€ really does mean react-native canā€™t find the module : |

sekao02:07:23

i think i fixed it, by installing react-navigation globally... npm install -g react-navigation

liesbeth10:07:50

@oskarth Some time ago you asked ā€œIā€™m unable to start the app at all, getting a red ā€œUnexpected identifier ā€˜GETā€™.ā€ in the simulator.ā€ Have you found a solution for that problem? If so, I would be very interested, as I am experiencing the same thing!

liesbeth10:07:47

Somehow the issue has resolved itself. I hope it has for you too!

carocad10:07:37

@liesbeth I get that error all the time in my workflow. It is pretty simple to solve though

carocad10:07:06

Are you using and Android device with USB connection?

carocad10:07:59

If so you should check the react native documentation on debugging with android device

carocad10:07:32

You need to enable port forwarding for adb

liesbeth11:07:25

Thanks for the tip, it works now!

carocad11:07:58

See Using real Android device in re natal readme

mfikes22:07:22

I always get this GET error if I start up the app i the simulator without first having Figwheel running.

oskarth14:07:42

@liesbeth don't remember this problem specifically but IIRC it was just some connection issue that got resolved by restarting stuff / reconnecting to wifi network etc. Glad it got sorted!

oskarth14:07:00

I got this with iOS fwiw

zlrth19:07:55

I have regular react-native sliders that iā€™m transforming by 270deg to give me vertical sliders. The problem is that, when using flexbox the width of the pre-transformed slider is used to make the height (so to speak) of the slider. how do i :transform and set the coordinates of the slider separately?

zlrth19:07:33

code looks like this in case itā€™s helpful

[slider {:flex 1 :value @periods :maximum-value 50 :minimum-value 0 :style {:transform [{:rotate "270deg"}]} :on-value-change (fn [z] (dispatch [:set-periods z])) :step 1}]