react-native-config
eslint-config-react-strong
| react-native-config | eslint-config-react-strong | |
|---|---|---|
| 8 | 4 | |
| 4,746 | 4 | |
| 0.3% | - | |
| 3.7 | 3.9 | |
| about 2 months ago | 10 months ago | |
| Java | JavaScript | |
| MIT License | MIT License |
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.
react-native-config
-
Secure store API keys
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!
- Multiple Environments in React Native with Appcenter + Fastlane (Android only)
-
React Native Template Strong
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.
-
[Electrode-Native]: Pass config to miniapp and read that config.
have you looked at react-native-config?
-
Securing React Native Application
It’s recommended to use react-native-config and react-native-dot-env to place your secure key, endpoint.
-
Sharing the structure of my in-production app
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.
-
How can I store a secret in React Native?
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
-
Setting up Storybook for React Native/TypeScript (server, loader, iOS, Android)
There are a few ways to use environment variables in React Native, but I used react-native-config. Setup is very simple:
eslint-config-react-strong
-
React Native Template Strong
Additionally there are Prettier and TSConfig rules which will make it hard to create messy code.
ESLint with strict set of rules and plugins provided by eslint-config-strong.
-
ESLint Config for React and React Native Development
There are also TSConfig and Prettier config.
- ESLint config for React and React Native development
What are some alternatives?
react-native-dotenv - Load react native environment variables using import statements for multiple env files.
redux-toolkit - The official, opinionated, batteries-included toolset for efficient Redux development
react-native-code-push - React Native module for CodePush
eslint-plugin-react - React-specific linting rules for ESLint
electrode-native - A platform to ease integration&delivery of React Native apps in existing mobile applications
lint-staged - 🚫💩 — Run linters on git staged files
rootbeer - Simple to use root checking Android library and sample app
Detox - Gray box end-to-end testing and automation framework for mobile apps
eslint-plugin-import - ESLint plugin with rules that help validate proper imports. [Moved to: https://github.com/import-js/eslint-plugin-import]
react-native-keychain - :key: Keychain Access for React Native
react-native-template-strong - Quick, opinionated, documented and strong beginning for your next project. Template made with react-native-navigation, TypeScript and Redux.