Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Support SwiftPM in @react-native-harness/ui

已关闭
#212 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@mrousavy 已经在做这个了。

开始于 2026年10月19日。

  • #213 来自 @mrousavy —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
react-native, swift, typescript

调研方向

Start by inspecting the @react-native-harness/ui package’s podspec, package contents, native sources, and SwiftPM configuration conventions in React Native 0.88. Add a Package.swift, its autolinking name in swiftpmConfig, include the manifest in the npm package, and ensure native sources compile without CocoaPods prefix-header imports. Verify with npx react-native spm in a React Native 0.88 app; the app should build while CocoaPods support remains available.

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

描述

@react-native-harness/ui ships a CocoaPods podspec but no Package.swift. React Native's SwiftPM autolinker therefore cannot build HarnessUI in an app that uses SwiftPM for its native dependencies.

This affects the published 1.5.0 package and the current 1.6.0 source on main. We hit it while moving Nitro's example app to React Native 0.88 and SwiftPM: https://github.com/margelo/nitro/pull/1781.

To reproduce, install @react-native-harness/ui in a React Native 0.88 app and run npx react-native spm. The dependency has no package manifest, so the autolinker requires a locally scaffolded manifest before the app can build.

The UI package should ship a SwiftPM manifest and its autolinking name in swiftpmConfig, including the manifest in its npm package. Its native sources also need to compile without CocoaPods' implicit prefix-header imports. The existing podspec can remain for CocoaPods apps.

I will send a PR for the native UI package. Harness's runner already accepts a built app; this does not require changing how tests run or adding SwiftPM support to optional native coverage.

主要语言
TypeScript
星标
333
派生
20
平均合并
14 小时
30 天内合并 PR
30

环境准备

从这里开始

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

callstackincubator/react-native-harness 的其他 Issue

查看 callstackincubator/react-native-harness 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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