#env-var #expo #local-file #cli-tool #json-file #eas #react-native

app eas-env

A simple CLI tool to manage environment variables for Expo projects

5 releases

0.2.2 Apr 19, 2024
0.2.1 Mar 25, 2024
0.2.0 Mar 24, 2024
0.1.1 Mar 24, 2024
0.1.0 Mar 23, 2024

#406 in Command line utilities

Download history 231/week @ 2024-03-18 134/week @ 2024-03-25 60/week @ 2024-04-01 111/week @ 2024-04-15 9/week @ 2024-04-22 41/week @ 2024-05-20 93/week @ 2024-05-27 43/week @ 2024-06-03 81/week @ 2024-06-10

258 downloads per month

MIT license

8KB
124 lines

Installation

Cargo

You will need to install rust and cargo to run this cli. You can do so by following the instructions here.

cargo install eas-env

CURL

curl -sSL https://raw.githubusercontent.com/corasan/eas-env/main/install.sh | bash

Releases

Download the latest release from the releases page and add it to your path.

Usage

By default, the program will use the default profile in your eas.json. You can specify a different environment by passing the profile as an argument. Note that this needs to be run in the root of your project and you will need to add your environment variables to the EAS profile.

eas-env
# creates .env.local file using default profile

eas-env -p production
# creates .env.local file using production profile

You can also specify the path to the app's directory where the eas.json file is located, useful if the project is in a monorepo. The default path is the current directory where the command is run.

eas-env --app-dir apps/mobile
# creates .env.local file using default profile inside apps/mobile directory

To make things easier you can add it to your package.json:

{
  "scripts": {
    "env:dev": "eas-env -p development",
    "env:prod": "eas-env -p production",
    "env:preview": "eas-env -p preview",
  }
}

Then you can run npm run env to create the .env.local file with the default profile.

Dependencies

~2–13MB
~107K SLoC