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

Control `pathSuffix` option via configuration file(s)

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

还没有人认领这个 Issue。

评估

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

调研方向

未指定源文件或测试。首先追踪 pathSuffix 如何传递给 Babel 插件和宿主包 CLI,包括 pod install 或 Gradle 构建期间的 NODE_API_PATH_SUFFIX,同时检查 pull request 104 可能带来的影响。当应用范围或按库配置能够在无需单独运行时设置的情况下始终一致地控制该选项时,即视为完成。

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

描述

enhancement Host 🏡 Linking 🔗 question

We're performing a transformation of the Node-API addon dynamic library paths on disk to their dynamic library names as they're linked into the host package.

Here's the documentation for the pathSuffix option of the NamingStrategy:

Controls how the path of the addon inside a package is transformed into a library name.
The transformation is needed to disambiguate and avoid conflicts between addons with the same name (but in different sub-paths or packages).

As an example, if the package name is my-pkg and the path of the addon within the package is build/Release/my-addon.node:

  • "omit": Only the package name is used and the library name will be my-pkg.
  • "strip": Path gets stripped to its basename and the library name will be my-pkg--my-addon.
  • "keep": The full path is kept and the library name will be my-pkg--build-Release-my-addon.

In the current state, this pathSuffix option is passed to the babel plugin as well as to the host package's CLI (either through a CLI runtime option or more likely the NODE_API_PATH_SUFFIX environment variable while running pod install or the Gradle build) and they need to match for the app to find the dynamic library files at runtime.

It would be more flexible and less brittle if ☝ was instead determined by

  • a single app-wide configuration setting, either in configuration file (or a key in the App's package.json) and / or
  • by individual per-library configuration files (or a key in their package.json files)

[!NOTE]
This will likely all change once https://github.com/callstackincubator/react-native-node-api/pull/104 merge.

主要语言
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 摘要。