You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[eas-cli] Add deno package manager support for builds
Detect deno as the package manager when a project (or its workspace
root) has a deno.lock lockfile and no Node package manager lockfile.
During builds, install dependencies with `deno install` (`--frozen`
when a frozen lockfile is requested), run the Expo CLI through
`deno run -A npm:expo`, and execute EAS build lifecycle hooks with
`deno task`, deno's equivalent of `<packageManager> run`.
deno.lock is also accepted by the lockfile presence check, and 'deno'
is a valid requiredPackageManager metadata value and
EAS_FALLBACK_PACKAGE_MANAGER value.
Detection lives in build-tools for now because @expo/package-manager
has no deno support; a Node lockfile always wins over deno.lock, so
existing projects are unaffected.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@ This is the log of notable changes to EAS CLI and related packages.
8
8
9
9
### 🎉 New features
10
10
11
+
-[eas-cli] Detect deno as the package manager for projects with a `deno.lock` lockfile, and use `deno install` / `deno task` during builds. ([#3951](https://github.com/expo/eas-cli/pull/3951) by [@yyq1025](https://github.com/yyq1025))
12
+
11
13
### 🐛 Bug fixes
12
14
13
15
-[eas-cli] Retry uploading assets that don't finish processing during `eas update`, instead of failing the update. ([#3918](https://github.com/expo/eas-cli/pull/3918) by [@gwdp](https://github.com/gwdp))
0 commit comments