Support statically linked addons
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 8/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- cmake, react-native, typescript
调研方向
This is a design discussion, not a patch: the issue asks how addons can be linked statically rather than loaded via dlopen (see #498). Read the four questions in the body (entry-point collisions, registration, the cmake-rn and ferric build outputs, and Node-API symbol resolution through weak-node-api or a Hermes stub) and the linked #263. Done means a written proposal that answers them, not code.
由索引模型根据 Issue 内容生成。
描述
Tracks interest in addons statically linked into the app, as opposed to loaded from a dynamic library. Node.js offers this through process._linkedBinding("foo"), for addons registered at startup. Originally raised in #263.
This isn't planned. It needs significant design work, so please add a 👍 or describe your use case if you'd need it.
It doesn't fit dlopen(module, filename) (#498), because there's no library to open. Some of the questions a design would have to answer:
- Entry points: every addon exports the same
napi_register_module_v1symbol, so two addons would collide when linked into one binary. - Registration: how an addon registers itself and under what name, given that
napi_module_registeris deprecated. - Build: what
cmake-rnandferricproduce, and howlinkgets it into the app, since today's prebuilds are dynamic libraries. - Node-API symbols: how a static addon reaches Node-API, with
weak-node-apior a Hermes stub.
- 主要语言
- TypeScript
- 星标
- 206
- 派生
- 12
- 平均合并
- 4 小时 35 分钟
- 30 天内合并 PR
- 9
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
callstackincubator/react-native-node-api 的其他 Issue
-
Android 🤖
难度 2/5 1-3 小时 新手友好度 66/100
callstackincubator/react-native-node-api#379 ·
维护者通常 1 天内回复
-
Sanity check of Hermes source directory via environment variable, when building Android projects未关闭Android 🤖 good first issue
难度 2/5 1-3 小时 新手友好度 78/100
callstackincubator/react-native-node-api#163 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement good first issue gyp-to-cmake
难度 2/5 1-3 小时 新手友好度 72/100
callstackincubator/react-native-node-api#161 · 3 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
enhancement Linking 🔗
难度 4/5 3-5 天 新手友好度 35/100
callstackincubator/react-native-node-api#497 ·
维护者通常 1 天内回复
-
Prebuilt node-api facade for published addons可能已有人在做 @kraenhansen 于 21 天前认领。 未关闭enhancement Host 🏡 Linking 🔗
callstackincubator/react-native-node-api#496 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 callstackincubator/react-native-node-api 的全部 Issue
相似的 Issue
-
[UI] Guard webApis against undefined window in SSR environments可能已有人在做 @madhavzanwar 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
headroomlabs-ai/headroom#4992 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
paperclipai/paperclip#22575 ·
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 82/100
lingdojo/kana-dojo#34502 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
bug frontend good first issue help wanted
难度 2/5 1-3 小时 新手友好度 86/100
nikhilb2/simple_invoicing#935 ·