Tell: elm-native-expo-counter upgraded to React Native 0.55 / Expo 27


#1

For anyone interested, with help from nateable, I’ve just managed to upgrade the opsb/elm-native-expo-counter project to the newest React Native 0.55 / Expo 27, and published the tweaked version at akavel/elm-native-expo-counter.

Wut is this?

The project is a simple example of using Elm with Expo, which allows to build mobile (Android/iOS) apps with Elm, without installing Android SDK/iOS equivalent. Expo is a “stub” Android/iOS app, which exposes many platform APIs to a JavaScript engine. Those then, via React Native bindings, are exposed to Elm. The project is based on ohanhi/elm-native-ui.

Important notes

  • The project is still at alpha/experimental stage, as it was before.
  • I only upgraded ohanhi’s and opsb’s projects to work with newest RN/Expo. I don’t really understand what’s going on underneath, neither claim to be now an active maintainer of any of the projects. That said, I’d like to try using them for some apps, so I’m at least hoping to slowly hack on them further and maybe learn something. Any help and explanations appreciated!
  • Big thanks to nateabele, who miraculously published a crucial piece of his own work on upgrading elm-native-ui to RN 0.55 at exactly the time I needed it and by luck accidentally stumbled upon it. I would most certainly fail if not his sudden deus ex machina post out of nowhere just an hour before I had to exactly copy-paste his nontrivial tweaks into my fork.
  • The fork of elm-native-ui I use in this project has a somewhat ugly hack in the “native” (JS) code, which makes it easier to embed it as a subdirectory, and properly see any errors in it. Similar hacks would be needed in the remaining .js files if you need to use corresponding modules.
    • I would GREATLY APPRECIATE if someone could help me how to properly remove this hack. I wish akavel/elm-native-ui could be used in projects not named literally user/project, and at the same time any Elm errors in it would not result in the super unhelpful in this case “letting too much stuff through” error message when compiling with elm-make (as happened to me when I tried to use elm-github-install a.k.a. elm-install). Sorry if that request is hard to understand :frowning: hope someone knows what I’m talking about…

#2

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.