[erenbati]

Why

Fixes #4205.

EAS CLI currently bundles an older Expo config-loading stack that can fail to read valid TypeScript app.config.ts files in two cases:

• configs that use import.meta can fail when the bundled fallback is evaluated as CommonJS
• TypeScript 7 exposes no compiler API through the typescript package stub, so the older require-utils path dereferences a missing ModuleKind.CommonJS

The SDK 56 config stack already contains the fixes for both cases.

How

• update the bundled Expo config stack to the SDK 56 line:
  • @expo/config@56.0.14
  • @expo/config-plugins@56.0.16
  • @expo/prebuild-config@56.0.23
  • this resolves @expo/require-utils@56.1.7
• preserve the legacy splash validation read after the SDK 56 config type change
• narrow update workflow typing to the platforms EAS Update actually publishes
• adapt the exempt-encryption memfs test mock to SDK 56's resolveFrom-based config path resolution
• regenerate yarn.lock

Test Plan

The original validation run on the pre-refresh branch passed the TypeScript 7 and import.meta reproductions, workspace build, fallback and exempt-encryption tests, typecheck, formatting, lint, and all 325 Jest suites: https://github.com/erenbati/eas-cli/actions/runs/34762593768

After merging current upstream main at f949f34 (head 6675cdd):

• corepack yarn workspace eas-cli typecheck-for-build passed
• bundled-config fallback tests passed (3/3)
• the update command and exempt-encryption test suites passed
• the full Jest suite on Windows passed 329/363 suites; remaining failures include POSIX path and locale assumptions, and the publish/PNG validation tests need Linux CI confirmation
• the root workspace build reaches copy-new-templates but its mkdir -p command is not supported by the Windows shell
• the latest PR Actions runs are waiting for maintainer approval (action_required); they have not run on this head

Checklist

• I've added an entry to CHANGELOG.md if necessary.

[erenbati]

/changelog-entry bug-fix [eas-cli] Update the bundled Expo config stack so TypeScript app.config.ts files work with import.meta and TypeScript 7.

[github-actions]

Subscribed to pull request

File Patterns	Mentions
packages/eas-cli/**	@douglowder
packages/eas-cli/src/commands/update/**	@wschurman, @quinlanj
packages/eas-cli/src/build/**	@sjchmiela

Generated by CodeMention

Warning: The preamble and epilogue options in commentConfiguration are deprecated. Use template instead.

[erenbati]

Updated this PR's branch with current upstream/main via a non-force fast-forward push of merge commit 497946a (parents 6675cdd + d02de4d). This resolves the conflicts in packages/eas-cli/package.json and yarn.lock while preserving the SDK 56 Expo config dependencies and accepting current workspace versions of @expo/eas-build-job / @expo/eas-json. Confirmed yarn install --immutable and yarn workspace eas-cli typecheck-for-build pass. Focused Jest suites (update/index, exemptEncryption) pass 28/28 tests. A broader 74-test Windows run had 2 POSIX-path expectation failures (publish-test.ts, expoConfig.test.ts); I am not claiming a full-suite pass. The umbrella Lerna build also failed only in the Unix-style mkdir step when copying CLI templates on Windows. GitHub now reports mergeable: true; CI/reviewer approval is still needed.

[erenbati]

Follow-up: I added a focused regression test in commit cfe260f for both independent reproductions in #4205. It exercises the actual EAS CLI @expo/config dependency loading a regular TypeScript app.config.ts, and the @expo/config resolved by @expo/prebuild-config loading a TypeScript config using import.meta. Both cases pass on Windows; the combined focused Jest run is 30/30 tests, eas-cli TypeScript typecheck passes, and the new file passes oxlint/oxfmt checks. No production code changes in this follow-up commit.

The new head still has four GitHub Actions workflows marked action_required (tests, GraphQL schema check, changeset check, AI code review), with no jobs run yet; these require upstream workflow authorization, rather than indicating test failures. The PR is mergeable but still blocked on those checks/review. I am leaving it open for maintainer approval.