fyi
discussions-and-proposals
fyi | discussions-and-proposals | |
---|---|---|
13 | 37 | |
671 | 1,612 | |
3.3% | 0.4% | |
8.1 | 5.0 | |
8 days ago | 17 days ago | |
JavaScript | ||
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fyi
-
Help regarding Expo & RN CLI
So i found out this client was using unimodules for a lot of his libraries. But unimodules has been deprecated and merged into expo now. So now I followed the instructions here, and it looks like I just have migrated my application into expo only as it(expo-upgrade) created created a .expo folder now and also bumped package.json libraries to latest versions.
-
🚀 New updates and improvements from Expo documentation this week
TLDR - Released new updates on EAS Update branch promotion flow deployment pattern to use a separate channel for each production runtime version release build: https://docs.expo.dev/eas-update/deployment-patterns/#branch-promotion-flow - Updates from Expo Modules API getting started guide: When importing a module in your app, you can now use relative paths: https://docs.expo.dev/modules/get-started/#using-the-module. You can still use absolute paths to import the module when creating it locally by using an additional configuration: https://github.com/expo/fyi/blob/main/absolute-path-expo-modules.md - EAS Build serves most dependencies & CocoaPods artifacts from a cache server for Android & iOS. However, in your project if you've ios directory & want cache Podlock.lock you can use paths property in eas.json: https://docs.expo.dev/build-reference/caching/#ios-dependencies - You can always look into EAS Build server infrastructure doc to learn more about the current configurations for Android and iOS build servers: https://docs.expo.dev/build-reference/infrastructure/ - With expo-updates, you can always check for updates manually if they are working or not. Check out the example: https://docs.expo.dev/versions/latest/sdk/updates/#check-for-updates-manually - Hermes apps use this debugging technique automatically when you open the debugger in Expo Go or a development build. For more in-depth info about check out the section on remote debugging: https://docs.expo.dev/guides/using-hermes/#can-i-use-remote-debugging-with-hermes - To add expo-updates to an existing React Native project, you need to configure your project. We recently updated the guide that works with latest React Native version: https://docs.expo.dev/bare/installing-updates/
-
Upgrading to Expo SDK 48 - Firebase analytics issue
I followed the instructions here: https://github.com/expo/fyi/blob/main/firebase-migration-guide.md
-
Unable to send push notifications with APN (Apple Push Notification Service) through Node server.
I got the DevicePushToken and sending APN push notification in the backend with Node, but I just couldn’t get it work in Expo (managed workflow). I followed exactly in docs which poorly documented and I also tried exactly like this.
-
Can't publish to Play Store
Has anyone had success with this tutorial from Expo? We've followed the steps here (https://github.com/expo/fyi/blob/main/creating-google-service-account.md), but in Step 8 ("Return to the API access page on the Google Play Console and ensure it shows your new service account. Click on Grant access for the newly added service account.") the service account just isn't listed.
-
Using Expo and Realm with expo-dev-client
This will create a prebuilt Expo app. That is, you'll see ios and android folders in your project and this won't be a managed Expo app, where all the native details are hidden and Expo takes care of everything. Having said that, you don't need to go into the ios or android folders unless you need to add some native code in Swift or Kotlin.
-
Build an Offline-First React Native Mobile App with Expo and Realm
Right now, Realm is not compatible with Expo Managed Workflows. In a managed Workflow Expo hides all iOS and Android native details from the JavaScript/React developer so they can concentrate on writing React code. Here, we need to prebuild our App, which will mean that we lose the nice Expo Go App that allows us to load our app using a QR code.
-
What is the core limitations of Expo for RN?
The smaller bundle size is also being worked on. Not quite sure what their timeline is, but I think it's pretty soon? See here: https://github.com/expo/fyi/blob/master/managed-app-size.md and/or watch this: https://www.youtube.com/watch?v=7E6zsRpfT4U
- Does Expo 41 (bare workflow) work with RN 0.64?
- How to reduce ReactNative app size?
discussions-and-proposals
-
Rn-fetch-blob build error
Removing package name from AndroidManifest.xml is required for RN 0.73. Libraries is started to remove it and switched to namespace since RN 0.71. You have 2 options:
-
React Native
React Native: A JavaScript Framework for Building Native Mobile Apps
- Is community doing something to improve developer experience?
-
Front-end Guide
Before you dive into the various aspects of building a JavaScript web app, it is important to get familiar with the language of the web - JavaScript, or ECMAScript. JavaScript is an incredibly versatile language which you can also use to build web servers, native mobile apps and desktop apps.
- In case someone missed it: How can we improve React Native? · react-native-community/discussions-and-proposals
- 2022: How can we improve React Native?
-
What bothers you about react native?
there are a whole bunch of complaints here
- 2022: How can we improve React Native? - We (the React team) are looking into your opinion and suggestions on how we can improve the developer experience of React Native - Thread closes in ~2 weeks.
-
Setting up React Native Monorepo with Yarn Workspaces
Using a monorepo is growing in popularity - there is even an open proposal to migrate react-native repository to monorepo. Find out more about React Native monorepo on github.
-
Create high-performance graphics with React Native Skia
React Native JSI is a core change in the re-architecture of React Native. This is a layer that offers “synchronous” communication between JavaScript and native code. It will be replacing the default react native bridge. (Source)
What are some alternatives?
expo - An open-source framework for making universal native apps with React. Expo runs on Android, iOS, and the web.
react-native-skia-demo - A React Native Project demonstrating use of react-native-skia library
async-storage - An asynchronous, persistent, key-value storage system for React Native.
WebdriverIO - Next-gen browser and mobile automation test framework for Node.js
realm-js - Realm is a mobile database: an alternative to SQLite & key-value stores
expo-native-starter-kit - This starter kit let's you run expo and ejected app together. Which means you can add native modules to your code and still be able to take advantage of expo's development environment
Realm - Realm is a mobile database: a replacement for Core Data & SQLite
Cypress - Fast, easy and reliable testing for anything that runs in a browser.
read-it-later-maybe - Offline-First React Native Mobile App with Expo and Realm
caldera-react - Server-side execution for React 🌋