This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-07
Channels
- # announcements (7)
- # beginners (123)
- # calva (27)
- # cider (23)
- # clj-kondo (4)
- # cljsrn (7)
- # clojure (29)
- # clojure-dev (7)
- # clojure-europe (4)
- # clojure-italy (4)
- # clojure-nl (16)
- # clojure-uk (47)
- # clojurescript (1)
- # code-reviews (4)
- # cursive (4)
- # data-science (4)
- # datomic (30)
- # duct (4)
- # fulcro (4)
- # graphql (1)
- # kaocha (4)
- # mount (8)
- # off-topic (13)
- # overtone (1)
- # pedestal (2)
- # planck (3)
- # re-frame (9)
- # reagent (50)
- # ring (12)
- # shadow-cljs (38)
- # spacemacs (5)
- # testing (13)
- # tools-deps (55)
- # vim (30)
- # xtdb (13)
Definitely make sure you have a known-good git commit to roll back to, then give it a shot. Re-natal itself is usually not the problem when I do upgrades, but React Native and some of the more complex dependencies I have underneath it. If you have a fairly vanilla project you should be ok, but as with any RN tooling/deps, no promises.
Ok, so speaking of upgrade troubles, I ran into the following one:
Some modules are apparently being loaded asynchronously by RN it seems like? I can’t find any documentation on this.
But I have a my-project.react
namespace with things like (def linking (.-Linking ReactNative))
to import modules.
Some of them (like Text
or Modal
) are available right away. Others do not load, and are only available when I load them later. Has anyone else dealt with this?
Hm, looks like the issue is actually that my custom native modules are erroring, and it just silently didn’t load the rest of the namespace after that happened.