Framework support

Dotvault for Expo

Dotvault for Expo and React Native apps.

Anything prefixed EXPO_PUBLIC_ is compiled into your app bundle, which means it ships to every device that installs it. There is no unsending that. Dotvault labels every EXPO_PUBLIC_ variable as client-exposed and annotates EXPO_TOKEN as the CI credential it is, so the two are told apart on sight rather than after a release.

What you get

  • →Detects Expo from package.json.
  • →Labels EXPO_PUBLIC_ variables as client-exposed, so what ships in the bundle is marked in the file.
  • →Warns when an EXPO_PUBLIC_ value can only be a secret. An app bundle sits on every device that installed it, so there is even less taking it back than usual.
  • →Recognises EXPO_TOKEN for CI and EXPO_DEVTOOLS_LISTEN_ADDRESS.
  • →Snapshot history across your development and production env files.

Known environment variables

Dotvault recognises these variables when you open a Expo project and surfaces helpful descriptions and warnings in the editor. Expo is detected via expo in package.json.

  • EXPO_PUBLIC_

    Client-exposed variable (Expo)

  • EXPO_TOKEN

    Expo access token for CI/CD

  • EXPO_DEVTOOLS_LISTEN_ADDRESS

    DevTools listen address

Official Expo docs: docs.expo.dev