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

Eliminate external subprocess dependencies (curl and wasmtime)

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

维护者通常 10 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
wasm, zig

调研方向

Start by locating the HTTP networking layer that invokes curl and the WASM runtime adapter that invokes the wasmtime CLI; the issue does not name specific files or tests. Read those entry points and assess native Zig HTTP and an in-process C WASM interpreter as separate pieces of work. Done means core networking and WASM execution no longer depend on external subprocesses while retaining the stated portability and minimal-footprint goals.

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

描述

enhancement
Description

This feature replaces the current use of external subprocesses for core functionality with native, in-process implementations. Specifically, it involves refactoring the HTTP networking layer to use Zig's native std.http.Client instead of shelling out to the curl binary, and updating the WASM runtime adapter to statically link a lightweight C-based WASM interpreter (such as wasm3 or the wasmtime C-API) rather than invoking the wasmtime CLI via child processes.

Motivation

NullClaw's primary value proposition is being a strictly self-contained, lightweight static binary that requires no external dependencies. Relying on host-installed tools like curl and wasmtime breaks this guarantee of true portability and introduces unnecessary performance bottlenecks due to continuous process-spawning overhead. By bringing these capabilities entirely in-process, we ensure the application remains completely standalone, reduces invocation latency, and fully adheres to its zero-dependency design philosophy while preserving a minimal memory footprint.

主要语言
Zig
星标
8.1k
派生
945
平均合并
7 天 6 小时
30 天内合并 PR
7

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

nullclaw/nullclaw 的其他 Issue

查看 nullclaw/nullclaw 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

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