@framers/agentos-ext-cloud-netlify

中文文档
0.1.5发布于 2026/11/11Apache-2.0TypeScriptES Module零依赖构建来源已验证近 30 天下载 2万

Netlify cloud deployment extension — deploy sites, manage domains, and configure environment variables via the Netlify REST API.

原始使用文档
文档目录10 节
  1. Installation
  2. Usage
  3. Configuration
  4. Tools
  5. netlifyDeploySite
  6. netlifyListSites
  7. netlifyConfigureDomain
  8. netlifySetEnvVars
  9. Notes
  10. License

Netlify cloud

This pack gives an agent tools to deploy sites from Git repositories, list sites, configure custom domains, and manage environment variables through the Netlify REST API.

Installation

npm install @framers/agentos-ext-cloud-netlify

Peer dependency: @framers/agentos >=0.10.40.

Usage

import { AgentOS } from '@framers/agentos';

const agentos = await AgentOS.create({
  extensionManifest: {
    packs: [
      {
        package: '@framers/agentos-ext-cloud-netlify',
        options: {
          token: process.env.NETLIFY_AUTH_TOKEN ?? process.env.NETLIFY_TOKEN,
        },
      },
    ],
  },
});

Configuration

OptionSecret idEnvironment variableRequiredDefault
tokennetlify.tokenNETLIFY_AUTH_TOKEN, then NETLIFY_TOKENYesEmpty string
secretsnetlify.tokenNoneNoContext secrets, then an empty object

The token resolves from options.token, the selected secret map, then the environment variables. options.secrets takes precedence over context secrets.

Tools

ToolWhat it does
netlifyDeploySiteDeploys a site from a Git repository URL and creates the site if it does not exist.
netlifyListSitesLists account sites with names, URLs, Git repositories, custom domains, and deployment states.
netlifyConfigureDomainHandles custom domain actions and returns DNS setup instructions.
netlifySetEnvVarsSets or lists site environment variables with deploy context scoping.

netlifyDeploySite

ParameterTypeRequiredDescription
gitUrlstringYesGit repository URL.
siteNamestringNoGlobally unique Netlify site name, derived from the repository name if omitted.
buildCommandstringNoBuild command.
publishDirectorystringNoPublish directory, such as dist, build, public, or .next.
branchstringNoGit branch to deploy from, default: main.
envVarsobjectNoSite environment variables as key-value pairs.

netlifyListSites

ParameterTypeRequiredDescription
limitnumberNoMaximum number of sites to return.

netlifyConfigureDomain

ParameterTypeRequiredDescription
siteIdstringYesNetlify site ID or name.
domainstringYesCustom domain, such as example.com or www.example.com.
actionstringNoadd, remove, list, or check; default: add.

netlifySetEnvVars

ParameterTypeRequiredDescription
siteIdstringYesNetlify site ID or name.
varsobjectNoKey-value pairs of environment variables to set.
actionstringNoset or list; default: set.
contextstringNoDeploy context: all, dev, branch-deploy, deploy-preview, or production; default: all.

Notes

Activation requires a Netlify personal access token. It fails if the token is missing or the current-user authentication request fails.

The Git URL parser accepts GitHub, GitLab, and Bitbucket URLs. Deployment reuses a site found by name or attempts to create it when lookup fails. Repository and build settings are passed when creating a site. The tool triggers a deployment and returns its state without waiting for completion.

Deployment, domain configuration, and environment variable writes modify remote resources. Domain setup returns DNS instructions; it does not create DNS records. The check action reads Netlify DNS zones and records.

The remove action passes an empty custom domain to the service, but the service omits empty values from its update request. The tool reports removal without sending a domain-clearing field.

Setting environment variables requires a nonempty vars object. With an account slug, variables use the account environment API and the selected context. Without an account slug, writes fall back to site build settings and omit context scoping. Listing returns values supplied by the API. The site mapper omits build environment values, so the build-settings listing fallback returns an empty array.

License

Apache-2.0

版本与发布记录

@framers/agentos-ext-cloud-netlify 共发布 6 个版本,首次发布于 2026/05/02;过去 12 个月发布了 6 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
0.1.5latest2026/11/114 天前
0.1.42026/10/2125 天前
0.1.32026/10/121 个月前
0.1.22026/10/111 个月前
0.1.12026/10/081 个月前
0.1.02026/05/026 个月前

关于 @framers/agentos-ext-cloud-netlify 的常见问题

@framers/agentos-ext-cloud-netlify 是什么?

Netlify cloud deployment extension — deploy sites, manage domains, and configure environment variables via the Netlify REST API.

如何安装 @framers/agentos-ext-cloud-netlify?

在项目目录运行 npm install @framers/agentos-ext-cloud-netlify,或使用 pnpm add / yarn add / bun add。它还需要宿主项目提供 peer 依赖:@framers/agentos(>=0.10.40)。npm 7 及以上与 pnpm 8 及以上默认会自动安装必需的 peer 依赖,Yarn 需要手动安装。

@framers/agentos-ext-cloud-netlify 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@framers/agentos-ext-cloud-netlify 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@framers/agentos-ext-cloud-netlify 需要什么版本的 Node.js?

package.json 的 engines 字段要求 Node.js >=22。版本不符时 npm 默认只给出警告,开启 engine-strict 后会拒绝安装。

@framers/agentos-ext-cloud-netlify 可以商用吗?

@framers/agentos-ext-cloud-netlify 使用 Apache-2.0 许可。宽松许可:允许商业使用、修改和再分发,并附带明确的专利授权;分发时需保留许可与 NOTICE 文件,修改过的文件要注明改动。以上为概括,不构成法律意见,请以许可原文为准。

@framers/agentos-ext-cloud-netlify 的下载量有多少?

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

@framers/agentos-ext-cloud-netlify 还在维护吗?

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