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 摘要。