well, maybe everyone already know about it and using it - but you can use figwheel-react-native with nrepl. Meaning you can connect your cider (or any other IDE) and get so much awesomeness from the development Here short instruction https://github.com/decker405/figwheel-react-native/issues/7

yeah was fooling around with renatal the other day

natal is using ambly as a repl which does some modification on the native side of the app. figwheel-react-native has a beautiful hack which allows figwheel to run along with rn packager. Not a big change for the end user, but looks cleaner and allows much easier integration with the existing app (my case exactly)

re-natal is the forked natal which uses figwheel lol

lotsa great movement in build setups 😄

the nice win with the figwheel setup is chrome debugging

or maybe it was just easier for me to get a better experience with it

i was trying to figure out how to get the source maps working but i think its a webworker thing?

oh, I didn’t know about re-natal. Late for the party

don’t know about source maps or debugger - didn’t have any need in any of this. Repl covers staff for me

checked re-natal - it’s using figwheel-react-native ha. Small world

yeah its pretty nice

i probably ran into more issues than i had to because i just copy and pasted some stuff i was working on too late in the night but

debugging caught exceptions is pretty amazing, espcially with source maps

could be yeah, more checks better. Have you tried advanced optimization btw?

in react native land?

only to get the android demo going

in general, yeah

yeah, for some reason everywhere I see :simple for production build

interesting

might just be convention c&p'ed 😛

I’ve never been able to get builds to work with anything higher than :simple

could be yeah. I’m just a bit uncomfortable to release my app with the source code. Advanced compilation makes me much more comfortable

oh, hm, that’s weird. Could it be related to the absence of externs for the RN land?

theres a demo i pulled

for android

lemme google i assumed it was advanced compilation i was doing

yeah, pls

https://github.com/nicholaskariniemi/ReactNativeCljs

yep advanced

https://github.com/nicholaskariniemi/ReactNativeCljs/blob/master/watch.clj#L4

cool, then it’s possible

lots of churn tho

might be a react native version thing

interesting

arte are you using om next in yr app

not yet - I have an existing app with native UI and part of business logic in CLJS already. Now I’m learning om itself and tools around it

but hopefully yeah - soon I’ll migrate couple of screens to om

Perhaps Nicholas Kariniemi's ClojureScript code “survives” :advanced because it refers to React Native JavaScript symbols using strings.

ah yeah thats a crucial painpoint for advanced compilation (nods)

well, I guess proper externs would fix it?

FWIW, unchanged versions of Om worked against React Native when it came out. In other words, maybe React externs supplemented with a few more React Native externs would be sufficient.

nice

oh yeah, you are right

The React externs theoretically cover Om's usage, and the supplemental ones really only need to cover what your application code uses, I'd guess.

Yep, I’ll check

@artemyarulin: you do have an interesting point. I suppose anyone could download my Classroom Checkout app and at least steal the JavaScript source.

yeah

thats pretty interesting

well, this is an issue if RN itself

And since I open sourced Goby, they could have it all :)

Classroom Checkout uses :advanced, which I agree is pretty effective as an obfuscator :)

oh yeah. Well, for some people CLJS looks like obfuscated already

😛

Check out what Planck does—you can put your code in the binary.

I want to keep the main feature of RN - hot push without AppStore review

binary is not a choice unfortunately

Brave man :)

oh common - nothing scary there

(I'd be afraid I'd inadvertently break someone's app.)

But I suppose we do that all the time with web apps.

guys from the web doing it all the time and they don’t afraid

exactly!

well - OK, they afraid in any case

App Review is a joke IMHO

“If you afraid of deployment - you don’t have enough tests”(c) somebody

In other words, it shouldn't take a week

yeah, this is a just pain

actually without hot deploy it’s worser - once I released version with a bug and then I had to wait 10 days (!) in order to release a new version with a fix

ok, it wasn’t actually “once”

One thing that does scare me is the QTTT React Native thing I released broke with an iOS update. (But then again, that happens with half my apps anyway, native or hybrid).

how did it break?

Here it is. It used to work. Now doesn't.

https://appetize.io/app/8kap5c0m9r3wjjdm45c416rbug?device=iphone5s&scale=75&orientation=portrait&osVersion=9.1

HA!

tru magic

I know this bug and I send a PL to RN with a fix:)

Maybe change 9.1 to 8.4 on the URL

update RN and everything gonna be all right

Yep 8.4 works but 9.1 doesn't.

https://github.com/facebook/react-native/pull/1672 this one

Cool. That was built a long time ago.

Sweet!!

Yep. Rule #1 with RN - always keep it up to date

I helped mfikes, best day of my life!

Wow. If you look at that preamble we get at the beginning the JavaScript generated by ClojureScript, it is to deal with an integer multiplication error in Safari I helped David track down. :)

hah yeah i noticed that

Things don't feel fragile though. Just normal fairly rare errors. It's amazing all these JavaScript engines produce the same behavior for so much code.

We'll be stuck with that Safari integer multiplication fix for years. :)

Gotta go. I’ll play with advanced optimisation tomorrow - hopefully I’ll find a solution

Speaking of JavaScriptCore, you should at least compile with :static-fns true to avoid http://dev.clojure.org/jira/browse/CLJS-910

awesome heads up