react-native-dotenv VS react-query

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

react-query

React Query: This library makes it easy to manage data in your React applications, from fetching to caching and updating data. It offers a simple, powerful, and flexible API for handling data and keeping your UI in sync with your data. https://github.com/tannerlinsley/react-query

useQuery (react-query) (+) all from above (+) even more features (-) more complex, even the examples are complex, has more aggressive defaults (re-fetching every 2s)

see here Overview

Rapini is a new tool that can generate custom React Query hooks using OpenAPI (Swagger) files.

React Query is the gold standard for using async data declaratively with hooks. I ended up needing to modify even my simple useTimer hook to work more like useQuery to take multiple keys in order to work as an inner observable for other operators.

For most situations, I would recommend using a library like React Query. It handles a lot of common data-fetching boiler plate and already accounts for this useEffect() issue. Also, it supports Suspense if you want to use that.

At this point, I want to move on to the react-query cache management library. Give a brief overview and see how you can improve your developer experience with cache using this library.

There isn't the "service" concept in React. If you need to send off data you can just do so with fetch. If you need to load data and cache it so it can be used across components and unmounts, then something like react-query is what I'd recommend. But it's basically a combination of React Context, useEffect, and useState to manage the cache and lifecycle of a request.

react-query is pretty neat too. I default to that for most projects unless it's something unusual