Fork me on GitHub
#cljsrn
<
2019-05-07
>
lepistane05:05:28

that's nice a question from newbie. Should we upgrade our projects too?

joshmiller06:05:38

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.

joshmiller18:05:34

Ok, so speaking of upgrade troubles, I ran into the following one:

joshmiller18:05:51

Some modules are apparently being loaded asynchronously by RN it seems like? I can’t find any documentation on this.

joshmiller18:05:23

But I have a my-project.react namespace with things like (def linking (.-Linking ReactNative)) to import modules.

joshmiller18:05:06

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?

joshmiller19:05:38

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.