Repository navigation
Use Expo's current service names: Expo Simulators, Expo Hosting, Expo Build, and Expo Services for EAS on its own - #81
Merged
Conversation
… Build, Expo Workflows, and Expo Services for EAS on its own Expo renamed its services (https://docs.expo.dev/eas-to-expo/). Docs, CLI messages, the Viewer's build label, comments and test names follow. EAS CLI, the eas commands, eas.json, EAS_* error codes and the eas-simulator identifiers keep their names.
|
Viewer preview of 65ecc66 · reports from brentvatne/euxy#163
The link stays the same on every push. Deploy run |
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
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 and why
Expo renamed its services (EAS and Expo service names), and Expo Simulators launched under its new name. Docs, CLI messages, the Viewer's build label, comments and test names now use the current names:
These keep their names, as Expo's do: EAS CLI, the
eascommands,eas.json, theEAS_*error codes and environment variables, and identifiers such as theeas-simulatorprovider,simulator: eas,repack: easand.env.eas-simulator. Two test fixtures that quote eas-cli's own output ("…accessed on EAS builder…") are unchanged.Only wording changes: 95 files, 584 lines, each replaced one for one.
Screenshots
Text only, no screenshots taken. The Viewer's Inspector labels a screen's build id "Expo Build" instead of "EAS build". CLI output, for example:
starting an EAS Simulator session (iPhone 17, 30 min)starting an Expo Simulators session (iPhone 17, 30 min)reusing EAS build a81d5d80 …reusing Expo Build a81d5d80 …waiting for the hosted EAS repack <id>waiting for the hosted Expo Workflows repack <id>hosting the report on EAS Hostinghosting the report on Expo HostingNo EAS login was found.No Expo Services login was found.EAS simulator:start failed: …eas simulator:start failed: …Code examples
No change to usage.
Try it
Nothing to try.
Testing
npm run typecheck,npm run lint,npm run build,node scripts/pack-check.mjs,node --test test/node/*.test.mjs(1,713 pass),npm run test:hosting(25 pass),npm run test:viewer:artifacts(87 pass) andnpm run test:viewer:browser(48 pass). The Playwright e2e suite was not run locally; no e2e test asserts on a renamed string.Written by an agent (Claude Code) at Brent's request.