This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-16
Channels
- # admin-announcements (2)
- # bangalore-clj (3)
- # beginners (15)
- # boot (303)
- # carry (18)
- # cider (7)
- # cljs-dev (222)
- # cljsrn (103)
- # clojure (196)
- # clojure-czech (2)
- # clojure-russia (69)
- # clojure-spec (21)
- # clojure-uk (48)
- # clojurescript (68)
- # cursive (18)
- # datomic (185)
- # events (1)
- # hoplon (2)
- # lambdaisland (1)
- # leiningen (1)
- # mount (10)
- # off-topic (1)
- # om (14)
- # onyx (154)
- # parinfer (1)
- # pedestal (3)
- # planck (5)
- # protorepl (9)
- # re-frame (17)
- # reagent (27)
- # ring (2)
- # specter (58)
- # test-check (1)
- # testing (7)
- # untangled (59)
- # yada (35)
@doglooksgood: It compiles well but it crashes in runtime...
@pesterhazy: Any idea why I can’t get REPL nor reloading to work in brn?
@vikeri: haven't tried the repl in quite some time, so don't know what the status is there
but it should be possible to make it work, as it used to work
what I do is to change my on-js-reload
fn to prn
the result of a function to iterate quickly
obviously a repl would be quicker. Could you make an issue?
boot-reload should work out of the box. What kind of error do you get, if any?
@pesterhazy: Alright, I don’t get any errors or any indication that the on-js-reload
function is happening at all. I tried adding console.log statements to that function but nothing. I’ll create issues in boot-react-native
then.
are you looking at the device log?
there's react-native log-ios
(or log-android
)
that's where you see many of the important messages
it should work on android
did you forward the websocket port using adb
?
yes, you need it even for the emulator
as android emulators run in a VM
https://github.com/mjmeintjes/boot-react-native/wiki/Troubleshooting <-- see the section on Problem: console.error "Reload websocket error"
Ok, did not know that page. Maybe that should be added to the readme section about reloading.
@vikeri: I added a link to the troubleshooting guide to the homepage opening paragraph
@vikeri: TBH I haven't used the Chrome-based debugger much
some time ago I had some problems with it, but I haven't tried it lately
it certainly promises a better debugging experience
I usually just use the Red Screens (do you see those?)
if that fails there's usually something in the device log
the Red Screens are great because you can click on frames in the stacktrace, which opens an editor to the source file
Ok the reloading works in iOS, but I get the error Requiring unknown module ”../../../app/images/logo.png”
when it tries to reload. Strange.
that's a known issue!
what I do is to use (defonce logo (js/require ".../logo.png"))
that effectively works around the proble
@pesterhazy: Great! Now I’m getting weird issues with my subscriptions not conforming to spec. But that might have to do with something else...
@vikeri: added a section to the Troubleshooting Guide: https://github.com/mjmeintjes/boot-react-native/wiki/Troubleshooting
as some point we should look into why re-requiring images doesn't work with boot-reload (I have a suspicion, but am not sure)
yes I was going to do that
so you can link to specific problems
do you have a pointer to an example I can use?
this looks like a good example
@vikeri: did you get anywhere with your attempt to get node_modules into boot fileset?
@pesterhazy: Great! Nope, the folder is too big to be included, something to do with the attached filewatchers.
Could use the npm task but unsure of how that affects the rn packager so I skipped that for now...
what npm task do you mean?
ah boot-npm looks interesting
so a cache-dir is basically a tempdir that doesn't get deleted?
cool, yeah I suspect it'll be hard to make that work with the RN packager, which expects files in a certain location
but would be useful to try at some point
Another question, the packager
task in boot does not seem to work, what does it do that npm start — —reset-cache
does not?
nothing
it should be removed
IMO npm start
is the way to go, especially given that the xcode/android projects automatically start it in a terminal window
originally the idea was to run the packager from inside boot, but that turned out to be an uphill battle
complecting the various stages of the pipeline
quite often you want to restart the RN packager, but the cljs compiler rarely needs to be restarted; so it's better to keep them separate
also, the log output is best kept in a separate window, making things easier to grok for a beginner
would you mind opening an issue about this?
thanks
REPL not working in Android though, only in iOS. Tried adb reverse tcp:9001 tcp:9001
but it did not help.
interesting
an issue would be great, especially if you can reproduce it in SimpleExampleApp
what error do you see?
how about adding a boot task that automatically does that? That'd save people some trouble
hm yes, although that again goes against the separation of RN packager vs boot react naitve
ideally the RN team should fix https://github.com/facebook/react-native/issues/9084, but they've never even replied to any issue I've created
a PR to react-native? Not a lot of effort, but the chances of anything getting merged is slim I'm afraid.
hello! I'm trying to get the boot-react-native example to work, but it doesn't seem that the dev server is running on 8081? The only error I get is "Could not connect to development server" on the device
@shader: are you running SimpleExampleApp, and on ios or android?
@pesterhazy: Yes; recent clone of boot-react-native/example/app on a physical android device
@shader: so normally, if you run react-native run-android
, a packager window should open automatically
if it doesn't, you can run it manualy as @vikeri suggested
however, on many machines, retrieving the bundle takes a while when run for the first time
often the app gives up before the bundle is ready
you can try it on the command line using curl -o /tmp/bundle.js "localhost:8081/index.android.bundle?platform=android&dev=true&hot=false&minify=false"
if that blocks, you should see some progress in the packager terminal window
@shader: it's faster the second time
@shader: did you make it work?