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
Copy file name to clipboardExpand all lines: docs/src/content/docs/getting-started/environment-vars-config.mdx
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,6 +69,10 @@ const _buildTimeEnv = {
69
69
NEW_ENV_VAR=my-new-var
70
70
```
71
71
72
+
::: note
73
+
if you are not pushing env files to your repo(recomended), please make sure to check the [App releasing process](/ci-cd/app-releasing-process/#github-action-and-env-variables) to see how to create the env file on the fly before the prebuild script in the github actions.
74
+
:::
75
+
72
76
4. Make sure to run `pnpm prebuild` to load the new values.
The starter kit comes with a set of pre-installed and configured libraries. We recommend using these libraries for your project.
10
+
11
+
Below, we'll list other libraries we often use in our projects. These aren't included in the starter because:
12
+
13
+
1. They're for specific use cases.
14
+
2. They need a lot of setup.
15
+
16
+
This way, you can add them to your project only if you need them, keeping things simple to start with.
17
+
18
+
### State Management:
19
+
20
+
The starter kit comes with Zustand out of the box but if your application implements a lot of workflows, you might want to use [XState](https://xstate.js.org/) as it's more powerful on managing complex workflows and state machines.
21
+
22
+
For example, if you have a workflow to create a new card for user and this workflow has a lot of steps and conditions, Zustand might not be the best choice as it's more designed for simple state management and XState is your best choice in this case.
23
+
24
+
### Error Reporting:
25
+
26
+
-[Sentry](https://sentry.io/welcome/): very popular solution for error reporting in the javascript ecosystem and has a great integration with Expo.
27
+
28
+
### Notifications:
29
+
30
+
There is no solution fit all for notifications, but based on your use case we would recommend one of the following:
`\n☁️ For \x1b[1m\x1b[32mEAS Build\x1b[0m deployments, ensure the secret\x1b[1m\x1b[4m\x1b[31m${easEnvironmentFileVariable} \x1b[0m is defined in Project Secrets and has the proper environment file attached.`
218
+
`\n☁️ For \x1b[1m\x1b[32mEAS Build\x1b[0m deployments, ensure the secret\x1b[1m\x1b[4m\x1b[31m${environmentFiles[APP_ENV]} \x1b[0m is defined in Project Secrets and has the proper environment file attached.`
0 commit comments