feat(web): add start & build scripts for expo web#56
Merged
Conversation
ab7a2a8 to
ed399e1
Compare
💯 Test Coverage
😎 Tests Results
👀 Tests Details • (51%)
|
juanchoperezj
approved these changes
Sep 5, 2024
fernandatoledo
approved these changes
Sep 6, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does this do?
Add
start&buildscripts for Expo web.Why did you do this?
To support web as another platform like iOS & Android.
Who/what does this impact?
Projects needing to export for web.
How did you test this?
I added the comands and ran them locally. I tested all environments variables for all environments (development, staging, qa and production) were properly applied both when running the app (
pnpm run web) or building it (pnpm build:{environment}:web).