expo-asset is required by expo-font but never declared — blocks the last mobile test suite

[Miracle656]

Problem

components/__tests__/QuickActions.test.tsx fails to run:

FAIL components/__tests__/QuickActions.test.tsx
  Cannot find module 'expo-asset' from 'node_modules/expo-font/build/FontLoader.js'

expo-font/build/FontLoader.js requires expo-asset at runtime, but expo-font declares it in neither dependencies nor peerDependencies:

expo-font deps:  {"fontfaceobserver":"^2.1.0"}
expo-font peer:  {"expo":"*","react":"*","react-native":"*"}

frontend/mobile/package.json doesn't declare it either, and it is absent from node_modules after a clean npm ci. So nothing installs it and the require fails.

Why now

After #686 fixed the AsyncStorage mock, the mobile suite went from 10 failing suites to 1:

before #686   Test Suites: 10 failed, 19 passed, 29 total   Tests: 347 passed
after  #686   Test Suites:  1 failed, 28 passed, 29 total   Tests: 420 passed

Confirmed identically in CI and locally. This is the only thing left keeping Mobile — typecheck & test red.

That matters more than one suite: the job has been red on main for weeks, and PRs have been merged after establishing the red was pre-existing. A permanently-red required check trains everyone to ignore it, which is how a real failure eventually lands. Fixing this turns the check back into a signal.

What to build

Add expo-asset as a direct dependency of frontend/mobile, at the version matching the installed Expo SDK.

Suggested execution

1. npx expo install expo-asset — use expo install, not plain npm install, so the version is pinned to the SDK's compatible range rather than latest.
2. Confirm npx jest components/__tests__/QuickActions.test.tsx passes.
3. Run the full suite and confirm 29/29 suites pass.
4. Sanity-check the app still starts (npx expo start) — this adds a real package, not just a test shim.

Acceptance criteria

• expo-asset is declared in frontend/mobile/package.json at an SDK-compatible version
• npm ci && npx jest passes with 0 failing suites — paste the summary line
• Mobile — typecheck & test is green on the PR (this is the point of the issue; a green local run isn't sufficient evidence)
• The lockfile is committed and consistent

Notes

• frontend/mobile uses plain npm. Do not use --legacy-peer-deps — it corrupts the lockfile in this workspace.
• Do not "fix" this by mocking expo-asset in jest.setup.js. The module is genuinely required by a package we ship; the missing dependency is the bug, and mocking it would hide a real gap that could bite at runtime.

---

Drips Wave · Complexity: Easy · 100 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[uchesybil]

@uchesybil has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @uchesybil to this issue.

[babawo96]

@babawo96 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I have reviewed this issue and I would like to work on it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @babawo96 to this issue.

[Stanley-Owoh]

@Stanley-Owoh has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Good day maintainer please i would like to work on this issue
I can work on this immediately with positive results please assign it to me. Thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Stanley-Owoh to this issue.

[Davoski1]

@Davoski1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would love to work on this issue, please assign to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Davoski1 to this issue.

[AGWAM001]

@AGWAM001 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

ill love to work on this immediately after being assigned

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AGWAM001 to this issue.

[drips-wave]

Congratulations, @AGWAM001! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @AGWAM001: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊