Feature/Add environment variable injection feature in example-monorepos #496
Conversation
This file contains 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
Created ./generateEnv.js file to inject environmental variables into next and expo packages
Created a .env.example file to guide users in setting up environmental variables for Expo and Next.js packages.
Updated ./apps/expo/babel.config.js file to inject for seemless environmental injection into expo package
Updated /.gitignore file to ignore all .env and env.ts files
Updated /apps/expo/package.json file with react-native-dotenv and @types/react-native-dotenv pacakges
Updated scripts property of ./package.json to inject environmental variables into both next.js and expo packages when development server is started in web or native
Updated yarn.lock to reflect changes in ./apps/expo/package.json
Updated packages/app/features/home/screen.tsx to demonstrate usage of injected environment variables VAR_1 and VAR_2
Updated packages/app/features/home/screen.tsx to demonstrate usage of injected environment variables VAR_1 and VAR_2
Updated yarn.lock to reflect changes in ./apps/expo/package.json
Updated scripts property of ./package.json to inject environmental variables into both next.js and expo packages when development server is started in web or native
Created a .env.example file to guide users in setting up environmental variables for Expo and Next.js packages.
Created ./generateEnv.js file to inject environmental variables into next and expo packages
Updated /.gitignore file to ignore all .env and env.ts files
Updated ./apps/expo/babel.config.js file to inject environmental variables into next and expo packages
Updated /apps/expo/package.json file with react-native-dotenv and @types/react-native-dotenv pacakges
Created a .env.example file to guide users in setting up environmental variables for Expo and Next.js packages.
Created ./generateEnv.js file to inject environmental variables into next and expo packages
Updated /.gitignore file to ignore all .env and env.ts files
Updated yarn.lock to reflect changes in ./apps/expo/package.json
Updated packages/app/features/home/screen.tsx to demonstrate usage of injected environment variables VAR_1 and VAR_2
Updated scripts property of ./package.json to inject environmental variables into both next.js and expo packages when development server is started in web or native
Updated yarn.lock to reflect changes in ./apps/expo/package.json
Updated ./apps/expo/babel.config.js file to inject environmental variables into next and expo packages
Updated /.gitignore file to ignore all .env and env.ts files
Created ./generateEnv.js file to inject environmental variables into next and expo packages
Created a .env.example file to guide users in setting up environmental variables for Expo and Next.js packages.
Updated yarn.lock to reflect changes in ./apps/expo/package.json
Updated ./apps/expo/babel.config.js file to inject environmental variables into next and expo packages
Updated /apps/expo/package.json file with react-native-dotenv and @types/react-native-dotenv pacakges
Updated scripts property of ./package.json to inject environmental variables into both next.js and expo packages when development server is started in web or native
Updated packages/app/features/home/screen.tsx to demonstrate usage of injected environment variables VAR_1 and VAR_2
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
@obedNuertey1 is attempting to deploy a commit to the BeatGig Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature: Environment Variable Injection Across Expo and Next.js Packages in example-monorepos
Why:
Currently, managing environment variables separately for both Expo and Next.js packages can be cumbersome. This PR adds a feature that injects environment variables from a single
.envfile into both Expo and Next.js, streamlining the process and ensuring consistency across both environments.What:
generateEnv.js) was created to pull variables from a.env.globalfile and inject them into Expo (EXPO_*) and Next.js (NEXT_PUBLIC_*)..env.examplefile was added to show how environment variables should be structured.References:
This PR addresses a previously closed issue related to environment variables management but goes further to automate the process.
For more context, see:
Using environmental variables example
Screenshots: