Created
July 5, 2019 09:48
-
-
Save FreddyPoly/3121ae61c2286bdbb1f975a109bff8a1 to your computer and use it in GitHub Desktop.
[REACT NATIVE] Env Var Setup Example
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// | |
// Load environment variables in. | |
// | |
// IMPORTANT: | |
// | |
// 1. These might be null, so fallback to sane defaults accordingly where you | |
// make use of these. | |
// | |
// 2. You must use this syntax: process.env.NAME_OF_ENV_VAR. No funny stuff | |
// or the babel plugin won't work. | |
// | |
// 3. You must whitelist each one in your `babel` config. | |
// | |
// GOTCHA: | |
// | |
// Babel will cache things extensively. In dev, to bust this cache to pick up | |
// new environment variable values, just change this file and resave it. | |
// | |
// Or run `yarn start --reset-cache` to nuke babel's cache entirely | |
// (overkill). | |
// | |
// ---------------------------------------------------------------------------- | |
// tell typescript that there will be a the `node.js` process global variable used | |
declare var process: any | |
/** | |
* An example importing an environment variable. | |
*/ | |
export const API: string | undefined = process.env.API | |
export const ENV_VAR_TEST: string = process.env.ENV_VAR_TEST = 'lorem ipsum' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment