@ai-ecoverse/wasm-curl

中文文档
8.22.0-10发布于 2026/10/22curl零依赖构建来源已验证近 30 天下载 2万

curl 8.22, the command-line URL transfer tool, with libcurl.

原始使用文档

@ai-ecoverse/wasm-curl

curl 8.22.0 and static libcurl for slicc's wasm realm. Mbed TLS backend (honors SSL_CERT_FILE / CURL_CA_BUNDLE), zlib, HTTP/1.1 only. Linked with slicc socket + select + spawn shims for loopback networking and the upcoming HTTP CONNECT / TLS proxy (http_proxy / https_proxy).

pnpm add -g @ai-ecoverse/wasm-curl
curl http://127.0.0.1:8080/

Consumers (e.g. git) link lib/libcurl.a plus the shipped Mbed TLS archives and lib/webcrypto-entropy.o; see lib/pkgconfig/curl.pc.

Names other than localhost and numeric IPv4 go to the kernel's resolver. Tailnet names need slicc-kernel ≥ 1.27.0 plus a page uplink (seven's Tailscale); then curl --noproxy '*' http://peer.your-tailnet.ts.net/ resolves and connects directly (IPv4 / A records only). Without them such names fail with "Could not resolve", as before.

8.22.0-8: the environment is the kernel's

curl -n finds ~/.netrc when HOME is unset, through the passwd entry's home, as on Linux (homescoop#724). Emscripten's glue used to fill a missing variable with its placeholders (HOME=/home/web_user, USER=web_user, PATH=/, …), so curl looked in /home/web_user. curl now links slicc-env.js, so it sees only the environment the kernel passes. env -i curl … gets no PATH=/ either.

8.22.0-10: the shared slicc-env.js, and /etc/hosts

curl links shims/slicc/slicc-env.js, the copy every homescoop_em_cli_ldflags link gets, instead of the copy in packages/coreutils (homescoop#1625). The build fails if the glue still has Emscripten's USER: "web_user" placeholders. With HOME unset, curl finds ~/.curlrc and ~/.netrc through the passwd entry's home and never looks in /home/web_user. Under env -i it sees no HOME, USER, LOGNAME, PATH, PWD or LANG.

Names in /etc/hosts (IPv4 lines, any case, with or without a final dot) resolve before the kernel's resolver is asked, as with musl (homescoop#580). Commented lines and ::1-only names don't resolve. Only root can edit the file.

curl is rebuilt and compared byte for byte in every ladder-pr (it's off scripts/reproducible-pending.json, #808).

版本与发布记录

@ai-ecoverse/wasm-curl 共发布 10 个版本,首次发布于 2026/09/29;过去 12 个月发布了 10 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
8.22.0-10latest2026/10/2214 天前
8.22.0-92026/10/2215 天前
8.22.0-82026/10/2016 天前
8.22.0-72026/10/1918 天前
8.22.0-62026/10/1720 天前
8.22.0-52026/10/1620 天前

关于 @ai-ecoverse/wasm-curl 的常见问题

@ai-ecoverse/wasm-curl 是什么?

curl 8.22, the command-line URL transfer tool, with libcurl.

如何安装 @ai-ecoverse/wasm-curl?

在项目目录运行 npm install @ai-ecoverse/wasm-curl,或使用 pnpm add / yarn add / bun add。

@ai-ecoverse/wasm-curl 支持 TypeScript 吗?

该包的 package.json 没有声明类型入口。需要类型提示时,可以在 npm 上查找社区维护的 @types/ai-ecoverse__wasm-curl 是否存在。

@ai-ecoverse/wasm-curl 可以商用吗?

@ai-ecoverse/wasm-curl 使用 curl 许可。声明的许可为 curl,请阅读许可原文确认使用条件。以上为概括,不构成法律意见,请以许可原文为准。

@ai-ecoverse/wasm-curl 的下载量有多少?

根据 npm 官方下载统计,@ai-ecoverse/wasm-curl 在 2026/10/05 – 2026/11/03 这 30 天内被下载 20,227 次,日均约 674 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@ai-ecoverse/wasm-curl 还在维护吗?

最新版本 8.22.0-10 发布于 2026/10/22(14 天前);至今共发布 10 个版本,其中过去 12 个月发布了 10 个;首次发布于 2026/09/29。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。