-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ENG-14625][eas-cli] add eas build:dev
command
#2820
Conversation
Subscribed to pull request
Generated by CodeMention |
Size Change: -289 B (0%) Total Size: 53.4 MB
|
my main concern here is implementing this as a top level command, which feels like something we'd be committing to - and we may want to use the |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2820 +/- ##
==========================================
- Coverage 52.71% 52.54% -0.16%
==========================================
Files 588 589 +1
Lines 22912 23036 +124
Branches 4782 4814 +32
==========================================
+ Hits 12076 12103 +27
- Misses 9882 9970 +88
- Partials 954 963 +9 ☔ View full report in Codecov by Sentry. |
@brentvatne What do you think about |
eas build:dev
command
eas build:dev
commandeas build:dev
command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few minor comments and one question about the build profile. Otherwise looks good to me. Will delegate to a reviewer more familiar with builds for approval though.
projectDir, | ||
}); | ||
const buildProfiles = | ||
buildProfilesOverride ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious (I'm not super familiar with build profiles), from a UX perspective should we require them to specify/choose an existing dev-client-enabled profile instead of creating a virtual profile for them? If not, are there any side effects of creating this "virtual" profile for them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I think what you suggest here might be a better option 🤔 The Current implementation should "magically" work well out of the box for users, but I think it limits the customization of things (like selecting the bun
version). I believe that using explicit profiles can also have the benefit of people having a good idea about what settings we apply under the hood for these builds 🤔 What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely a good question for the reviewers on this who are more familiar with build profiles. I unfortunately only have a very surface-level understanding of them. My comment was spurred by the more general idea that having "virutal"/"synthesized" things often does lead to confusion as you mentioned.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will delegate final approval to other reviewers more familiar with build.
projectDir, | ||
}); | ||
const buildProfiles = | ||
buildProfilesOverride ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely a good question for the reviewers on this who are more familiar with build profiles. I unfortunately only have a very surface-level understanding of them. My comment was spurred by the more general idea that having "virutal"/"synthesized" things often does lead to confusion as you mentioned.
5e655a5
to
58e0389
Compare
⏩ The changelog entry check has been skipped since the "no changelog" label is present. |
Why
https://exponent-internal.slack.com/archives/C1QLM27T9/p1734729481930599?thread_ts=1734708689.473259&cid=C1QLM27T9
Add
eas dev
command that:a. if we do - it downloads and launches them on the emulator/simulator using the same logic we use for eas build:run
b. if not - such a build is created and launched afterward
How
Do exactly what I mentioned above. Use as much code and functions from build logic and eas build:run that already exist to make it easier to maintain.
Test Plan
Test manually
https://exponent-internal.slack.com/archives/C1QLM27T9/p1736987685783579?thread_ts=1734708689.473259&cid=C1QLM27T9