react-native-config VS react-native

Best way to store API keys in RN? I need to store the google autocomplete API key somewhere but react-native-config and react-native-dotenv can be reverse-engineered. Any ideas? Thanks!

React Native Config bring you the ability, for example, to have different environments which will make it easier to work with different API endpoints and test your application.

have you looked at react-native-config?

It’s recommended to use react-native-config and react-native-dot-env to place your secure key, endpoint.

I put all my API keys and global config elements into here. I have a single file with an object which is indexed with they key PROD STAGE or DEV, which is pulled from a CURRENT_ENV.tsx file. I write to this file using a simple bash script and a make command. Alternatives to this are things like react-native-config but those packages don't obfuscate anything either so I could never justify their extra complexity.

Honestly, security wise it doesn't matter too much where you store it in the app. It'll be accessible one way or another. Common practice is that variables like this would be stored in a config/environment file. See: https://github.com/luggit/react-native-config

There are a few ways to use environment variables in React Native, but I used react-native-config. Setup is very simple:

Lastly, we just released a new version of React Native Storybook: RN Storybook 7. It brings major performance and compatibility improvements, including automatic story loading, improved error handling, stronger types, and much more.

There’s still a massive amount of potential with RN Storybook project and we’d love new contributors to help us get there. Find the project here and share your feedback, interest, or support.

I’m being tasked with migrating a “kitchen sink” of components (currently rendered with a feature flag & Stack navigation) to a more separate feature. They’ve decided on Storybook. I didn’t ask why as my contractor role wasn’t available to help w decision making at the time.

Also heres the pr where I'm adding support for require.context to React Native Storybook https://github.com/storybookjs/react-native/pull/501

Do you use Storybook? I ran into similar issues where promises didn't resolve due to this issue: https://github.com/storybookjs/react-native/issues/20

If those drawbacks aren't dealbreakers, then I think you will be happy with the results. However If you are unable to use this package because you need a native mobile experience then consider using @storybook/react-native. You could even use both if it makes sense for your use case.

I recently set up Storybook for a React Native/TypeScript project. It wasn't so different from using Storybook for web dev, but there were a few catches. I found their official tutorial to be outdated sometimes, and their Github README was up-to-date but didn't have all the information I wanted.

take a look at: https://github.com/storybookjs/react-native/issues/133