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

Support in-app Node-API addons

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
node.js, react-native, typescript
领域
api, mobile

调研方向

首先查看 PR-104 和示例应用,然后检查应用包是如何扫描依赖预构建版本的。确定支持哪些 Node-API addon 用例,并在应用源代码中实现 addon 示例。示例能够调用这些 API 且该用例已完成文档记录,即视为完成。

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

描述

documentation Host 🏡

We're mainly testing Node-API addons being build and published as separate shared libraries in library packages and it would be good to have explicit support for implementing and publishing Node-API addons as part of the app source-code as well.

This could be a few different things:

  • As a shared library built as part of building your app, i.e. a multi-arch prebuild included in your app directory. We do support this (as the app package is scanned when we're scanning dependencies for prebuilds), but we're not actively testing it - which we should.
  • An addon built as part of your app source-code, this should technically be possible, but we're lacking the merge of PR-104 adding support for the (soft deprecated) napi_module_register function, which would be the only way to register such a module / addon (as far as I know at least).

A large part of this effort would be implementing an addon in the example app to show the use of the APIs as well as documenting the use-case.

主要语言
TypeScript
星标
188
派生
10
平均合并
2 天 17 小时
30 天内合并 PR
3

贡献指南

这个仓库没有索引到贡献指南

从这里开始

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

callstackincubator/react-native-node-api 的其他 Issue

查看 callstackincubator/react-native-node-api 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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