This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-01
Channels
- # beginners (10)
- # cljs-dev (33)
- # cljsjs (4)
- # cljsrn (12)
- # clojure (39)
- # clojure-belgium (2)
- # clojure-russia (80)
- # clojure-spec (9)
- # clojure-uk (6)
- # clojurescript (22)
- # core-async (141)
- # cursive (2)
- # datomic (20)
- # devops (1)
- # emacs (20)
- # hoplon (1)
- # jobs (3)
- # lambdaisland (12)
- # leiningen (3)
- # lumo (44)
- # onyx (2)
- # pedestal (1)
- # quil (1)
- # re-frame (9)
- # reagent (4)
- # robots (1)
- # rum (3)
- # spacemacs (5)
- # uncomplicate (80)
- # untangled (46)
- # yada (2)
^ this was solved by tweaking node
's memory setting https://stackoverflow.com/a/38198512/4284484
I tried :advanced
on an iPad 2 and it brings my launch latency down to 2 seconds, where it was 3 seconds with :simple
. I think I might stick with :advanced
given that difference.
Thanks for the feedback @mfikes
@mfikes yea it took me a long time months ago to figure that out that you just did… the React Native bundler seems pretty inefficient/slow; but since I started using :advanced (my :advanced compiles cljs source is ~1.4MB of google closure JS vs. 5-6MB+ otherwise under :simple) I never had issues with the memory… tweaking the memory is also annoying because if you do it ad-hoc (aka edit the source, and I didn’t have patience for more proper fix), every time I upgraded React Native I had to re-fix the file lol
and I have definitely observed a similar thing, especially on older devices having larger JS file makes a big difference in the initial load times (and anecdotally/from my memory it got worse the bigger the :simple output); with the new ClojureScript externs auto generation it has been very pleasant using :advanced for the past 4-5 months and I never looked back 🙂
the React Native packager has various issues with big Javascript files. - /Users/r/s/wbl/node_modules/react-native/packager/src/JSTransformer/index.js increase transform timeout interval - Add --max_old_space_size=16384 to node command line - If you get node gc-timeouts -> https://github.com/facebook/react-native/issues/5196#issuecomment-237549879
https://github.com/drapanjanas/re-natal/issues/75 is also helpful with that issue
this is usually caused by (js/require)‘ing large json files and a large compiled js file. It is much better to use https://github.com/futurepress/react-native-static-server or a similar package
@eric.shao om-navigate is just an example of using react navigation in om-next, it's not a lib and certainly not popular 🙂