You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2023. It is now read-only.
The instructions on how to use environment variables doesn't seem to be up-to-date because react-native-dotenv isn't included in package.json.
Is this just some old code still laying around, or should the comment include some instructions that a user should add that package? Or should that package be included in the boilerplate?
Any update? I am using Ignite Flame and wondering the same thing. Instead of accessing the dev menu to toggle storybook UI (which doesn't appear to be working), I'd rather just pass a variable to expo start --storybook=true to run the story ok.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What's going on?
In the Ignite Bowser Expo template, there is an
.env
file. I can’t see that it is used in the boilerplate. It also says in the comment:The instructions on how to use environment variables doesn't seem to be up-to-date because
react-native-dotenv
isn't included inpackage.json
.Is this just some old code still laying around, or should the comment include some instructions that a user should add that package? Or should that package be included in the boilerplate?
Since the boilerplate now supports Expo, maybe
expo-constants
should be the preferred way of using environment variables. https://docs.expo.io/guides/environment-variables/At the same time, the folder
app/config/
contains files that allows a user to use those as some kind of environment variables.Steps to reproduce
.env
ignite doctor
results:The text was updated successfully, but these errors were encountered: