react-native-config standard - Agenda 2023-01-19 #2125
kelset
started this conversation in
Bundle Working Group
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Agenda notes
Where are we today
align-depsUse align-deps to help migrate apps to the New Architecture #1863react-native.config.jshttps://github.com/react-native-community/cli/blob/main/docs/configuration.md#configurationapp.json/app.config.jshttps://docs.expo.dev/workflow/configuration/app.jsonused in non Expo-projects? RNTA?expo-module.config.json(https://docs.expo.dev/modules/autolinking/)app.jsonhttps://github.com/microsoft/react-native-test-app/wiki/Manifest-(app.json)codegenConfigwhere do we want to be
🔴 = no support for new arch at all
🟡 = we can infer that it will probably work with the new arch based on. For example, we could use the same one that RNDirectory uses, based on the presence of the codegenConfig field in package.json
🟢 = library has our custom-setting field set to true
How can we get there?
react-native-configsection of package.json that is spec'd and is coherent with existing config approach (should 1:1 having areact-native.config.js/app.config.js) with a dedicated field for declaring new arch supportapp.jsonentirely while at it?Let's discuss!
react-native-librarysection would be a much better namereact-native-metadata/react-native-metais another broader alternative that would allow to keep everything within it and could potentially work along a future alsoreact-native-configreactNativeMetalooks like a winnerAction items
reactNativeMetaso that we can async fill the details of the specific fieldsBeta Was this translation helpful? Give feedback.
All reactions