feature request: Proposal: Evaluate migration from React Native CLI to Expo for improved DX and maintainability

未关闭
#6,971 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
react-native

调研方向

首先审查 Rocket.Chat React Native 项目当前的原生依赖,并检查它们与 Expo Dev Client 的兼容性。测试项目是否可以使用提议的 prebuild 方案运行,然后记录需要自定义原生支持的模块。完成标准是形成一份可行性研究,明确识别阻碍因素,并在可行的情况下制定分阶段迁移路线图。

由索引模型根据 Issue 内容生成。

描述

🎉 feature
Feature Description

Proposal: Evaluate migration from React Native CLI to Expo

Problem

The current Rocket.Chat React Native app is built using the React Native CLI and relies heavily on manual native configuration. This leads to:

  • Complex setup for new contributors
  • Dependency conflicts (Node/React version alignment)
  • Longer onboarding time
  • Increased maintenance overhead for native modules
  • Difficult environment reproducibility

During local setup, contributors often face issues related to:

  • Peer dependency mismatches
  • Native build configuration
  • Version compatibility
Proposed Direction

Explore the feasibility of gradually adopting Expo (prebuild/dev-client approach) to improve:

  • Developer experience
  • Faster onboarding for contributors
  • Easier dependency management
  • Reduced native configuration complexity
  • Improved testing and iteration speed

This does NOT necessarily mean a full immediate migration, but rather:

  • Evaluating compatibility with existing native modules
  • Identifying blockers
  • Creating a migration roadmap if feasible
Possible Approach
  1. Audit current native dependencies and Expo compatibility
  2. Test running the project using Expo Dev Client
  3. Document modules requiring custom native support
  4. Propose a phased migration strategy (if viable)
Motivation and Use Case
Expected Benefits
  • Faster setup for contributors
  • Reduced environment-related issues
  • Improved long-term maintainability
  • Easier experimentation and feature development
Implementation Ideas
Willing to Contribute

I would like to take ownership of:

  • Initial feasibility study
  • Dependency compatibility analysis
  • Proof-of-concept setup
  • Documentation for migration path

Would love feedback from maintainers on whether this direction aligns with project goals.

Is this feature available in the API or web version?

Available in API

Rocket.Chat Server Version

No response

Rocket.Chat App Version

No response

Device Name

No response

OS Version

No response

Additional Context

No response

主要语言
TypeScript
星标
2.4k
派生
1.5k
平均合并
1 天 15 小时
30 天内合并 PR
29

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

RocketChat/Rocket.Chat.ReactNative 的其他 Issue

查看 RocketChat/Rocket.Chat.ReactNative 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。