Add tree-shaking for unused Expo modules to reduce bundle size

[RUKAYAT-CODER]

Background

The project imports entire Expo modules but uses only a small subset of exports. Enable tree-shaking in metro config and webpack to eliminate unused code. This requires proper ES6 module exports and sideEffect: false configuration.

Description

Many Expo modules are imported in full even when only specific exports are used. By configuring Metro bundler and package.json correctly, we can enable tree-shaking to remove unused exports, reducing output size by 8-12%.

Current Behavior

Unused Expo module code bundled in production (~200KB of unused code)

Expected Behavior

Only used Expo exports included in bundle. Unused code automatically stripped by bundler.

Impact

📦 Direct bundle size reduction of 8-12%
⚡ Faster app startup
💡 Improved performance on low-bandwidth networks

Acceptance Criteria

• Configure metro.config.js to enable tree-shaking
• Add sideEffects: false to package.json
• Audit all Expo imports for unused exports
• Convert unused full imports to named imports
• Verify bundle size reduction with expo analyze
• Test app functionality - no missing dependencies
• Document tree-shaking configuration in dev guide

Implementation Hints

Update metro.config.js with inlineRequires: true. Set optimization: true in production. Use expo build:web --analyze to identify removable code.

Performance Metrics

Before:

• bundleSize: 2.8 MB

After (Target):

• bundleSize: 2.45 MB (-12%)

Related Issues

• Initialize TeachLink Mobile App (Expo + React Native) #1
• Implement Touch Gesture System #3
• Implement Offline Mode and Data Sync #4

[Richardkingz2019]

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

I am interested in working on this issue and I shall deliver promptly on this with qualitaively feedback. Barak de sallah

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

[drips-wave]

Congratulations, @Richardkingz2019! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @Richardkingz2019: 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 🌊