react-native-dotenv VS zustand

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!

To consume env variables in js code you'd need https://www.npmjs.com/package/react-native-dotenv — basically, it will allow to reference single variable in the js code and at compile time it will pick up current value from the config

It's not possible to use react-native-dotenv in native code files like `build.gradle` or `Info.plist`: https://github.com/goatandsheep/react-native-dotenv/issues/190

Then install the 'react-native-dotenv' library in your project with the below commands using NPM or Yarn.

While you still developing your app use this package https://www.npmjs.com/package/react-native-dotenv

I know, not a direct answer to your question, but if you're looking for file-defined custom properties, the typical solution is to use https://github.com/goatandsheep/react-native-dotenv

⚙️ Handel environment variables with react-native-env

There are a few special libraries from npm that are used to make all this work and we cover them all in the video. Specifically we needed an AsyncStorage library and dotEnv, a library to manage local environment variable for the application

It's time to use the Firebase project configuration in the Expo app. To do so, first install the Firebase SDK by running expo install firebase. Additionally, install react-native-dotenv by running npm install react-native-dotenv, so that environment variables can be imported in the app via an .env file. Next, add the module:react-native-dotenv plugin to the default Expo babel.config.js file.

We will be making use of the handy npm library react-native-dotenv

For our case, points 1 and 2 can help us provide a better way of handling updates in our rapidly updating application. I have used zustand for the application.

Daishi Kato, creator of Zustand and Jotai, says there are a few things we need to support RSC serialization:

Zustand

Link: https://zustand-demo.pmnd.rs/

For more code examples visit the documentation here

Have you ever wanted to learn state-management but it felt so overwhelming to get started with Redux? Or maybe you're already using Redux but don't want to take the burden anymore? If so, you might want to take a shot at Zustand! Its an amazing state management library that's easy to get started and maintain in a long run. In this post, we'll dive into creating & sharing stores with this tiny Redux alternative.

You add the current user state to a React Context or state management library, read from it on the top bar, and write to it after a user signs in. Done. No big deal, right?

Zustand

I tried using skipHydration inside my zustand store based on their docs, then rehydrating it inside my modal. So far im getting the same errors. https://github.com/pmndrs/zustand/blob/main/docs/integrations/persisting-store-data.md