This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-29
Channels
- # aws (1)
- # beginners (78)
- # boot (27)
- # cider (16)
- # clara (15)
- # cljs-dev (84)
- # cljsjs (13)
- # cljsrn (19)
- # clojure (65)
- # clojure-france (10)
- # clojure-italy (8)
- # clojure-russia (35)
- # clojure-spec (34)
- # clojure-uk (124)
- # clojurescript (50)
- # clojutre (3)
- # core-async (16)
- # data-science (18)
- # datascript (1)
- # datomic (9)
- # emacs (2)
- # flambo (3)
- # fulcro (55)
- # graphql (3)
- # hoplon (4)
- # jobs (2)
- # juxt (21)
- # keechma (6)
- # lumo (73)
- # off-topic (4)
- # om (10)
- # onyx (5)
- # parinfer (1)
- # pedestal (3)
- # re-frame (60)
- # reagent (19)
- # specter (24)
anyone got a guide for debugging re-natal?
i’m missing something basic. after i run lein prod-build
, what do i do to run the app (either from the simulator or a real device) without running figwheel? I get failed to something something importScripts
when i run react-native run-ios
or when i run it from xcode on my real device.
npm start
? that works on the template project re-natal init sampleProject
, but not on my app. on my app, it hangs here:
React packager ready.
Loading dependency graph, done.
@tetriscodes You can enable source maps, debug in Chrome, and set breakpoints, etc. https://github.com/drapanjanas/re-natal#enabling-source-maps-when-debugging-in-chrome
@mfm You need to run a release build. Either manually change the scheme in Xcode or react-native run-ios --configuration=Release
Error: ENOENT: no such file or directory, open 'node_modules/react-native/packager/react-packager/src/Server/index.js'
no dir node_modules/react-native/packager
@mfikes any idea here?
hmmm. Nevermind. Couldn’t find fs
and ran nvm use v8
and it worked
thanks @mfikes. i was able to get the re-natal init sampleProject
to work with a production build.
but, i’m getting a behavior i’ve seen other people get: JavaScript heap out of memory
. this is with :simple
optimization. i’m going to try :advanced
, soon. i was wondering if anyone had any pointers.
Yeah, you can futz with the node
command embedded in the script to try to give it more memory
(The script is visible / editable in Xcode under one of the “build” tabs… I don’t have a project handy.)
(roughly 2 seconds vs 3 for Vocabulario http://fikesfarm.com/vocabulario/)
Just updated cljs-expo-template
to support Expo v20. (Give it a shot via lein new expo your-project
). See the github page for more details.
https://github.com/seantempesta/expo-cljs-template/
Updates:
expo
“20.0.0”
@mfm, @mfikes's advice is good, another option is to use this trick: https://github.com/pesterhazy/re-natal-husk
it circumvents the packager issues and works with simple optimization (and should work with advanced ones as well)