@howone/agent-cli 0.5.5 → 0.5.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -33,8 +33,8 @@ howone workflows search "海报" && howone workflows run <app>/<workflow> --inpu
|
|
|
33
33
|
(原来在 SDK 的 `.agents/skills`,拆仓时移过来了)。沙箱里 `howone init app` 生成的工作区直接带上这一份。
|
|
34
34
|
|
|
35
35
|
`templates/vite/package.json` 里锁的 `@howone/sdk` 版本要和已发布的 SDK 一致。
|
|
36
|
-
|
|
37
|
-
npm
|
|
36
|
+
模板固定使用公共 npm 的 `@howone/sdk@3.0.0-beta.1`,无凭据的 `.npmrc` 将 `@howone/*`
|
|
37
|
+
指向公共 npm,不需要配置华为云私仓凭据。CLI 升级只更新模板和 Skill,已有 App 的依赖不会自动改写。
|
|
38
38
|
|
|
39
39
|
## npm 安装
|
|
40
40
|
|
package/bin/index.mjs
CHANGED
|
@@ -2346,12 +2346,12 @@ async function installTemplateDependencies(plan, json) {
|
|
|
2346
2346
|
maxBuffer: 10 * 1024 * 1024
|
|
2347
2347
|
});
|
|
2348
2348
|
} catch (error) {
|
|
2349
|
-
throw new CliError("E_DEP_INSTALL_FAILED", "Failed to install dependencies with bun. Check the install log below. For @howone/sdk 404/401/403 errors,
|
|
2349
|
+
throw new CliError("E_DEP_INSTALL_FAILED", "Failed to install dependencies with bun. Check the install log below. The template SDK is available on public npm without private registry credentials. For @howone/sdk 404/401/403 errors, check the project @howone registry points to https://registry.npmjs.org/, then run bun install again.", {
|
|
2350
2350
|
...error && typeof error === "object" ? {
|
|
2351
2351
|
stdout: "stdout" in error ? String(error.stdout ?? "") : void 0,
|
|
2352
2352
|
stderr: "stderr" in error ? String(error.stderr ?? "") : void 0
|
|
2353
2353
|
} : void 0,
|
|
2354
|
-
registryHint: "https://
|
|
2354
|
+
registryHint: "https://registry.npmjs.org/"
|
|
2355
2355
|
});
|
|
2356
2356
|
}
|
|
2357
2357
|
};
|
package/package.json
CHANGED
|
@@ -37,6 +37,19 @@ may return HTTP 404 for `/preview/wake`; report that Studio needs the matching p
|
|
|
37
37
|
|
|
38
38
|
## The loop
|
|
39
39
|
|
|
40
|
+
External coding agents install `@howone/sdk@3.0.0-beta.1` from public npm so local types and
|
|
41
|
+
definitions are available without company registry credentials. Keep the project's
|
|
42
|
+
`@howone:registry=https://registry.npmjs.org/` configuration for local installs. Cloud preview
|
|
43
|
+
and release builds use the platform-managed private registry for the same SDK version; Studio
|
|
44
|
+
also keeps its own private registry configuration. Do not copy cloud registry credentials to
|
|
45
|
+
the user's machine or change the App's SDK version merely to work around a registry error.
|
|
46
|
+
|
|
47
|
+
A local SDK download failure and a cloud dependency-install failure need different fixes.
|
|
48
|
+
For local failures, inspect the project registry and pinned version. If cloud build logs show
|
|
49
|
+
an SDK tarball being fetched from a missing npmmirror URL, report the failing dependency URL
|
|
50
|
+
and build/version ID as a platform registry or lockfile-resolution error. Repeated HowOne
|
|
51
|
+
login does not fix package downloads.
|
|
52
|
+
|
|
40
53
|
```bash
|
|
41
54
|
howone push -m "<what changed>" --json # upload changes, build on HowOne, return preview URL
|
|
42
55
|
```
|
|
@@ -105,5 +118,5 @@ Only after the user explicitly agreed, having seen the preview.
|
|
|
105
118
|
| `E_BUILD_FAILED` | build failed | read `details.build.log`, fix, push again |
|
|
106
119
|
| `E_SEAL_FAILED` | version rejected before build (functions, entities) | read `details`, fix, push again |
|
|
107
120
|
| `E_NOT_FOUND` | unknown app / version | re-check with `howone apps list` |
|
|
108
|
-
| `E_DEP_INSTALL_FAILED` | template dependency install failed |
|
|
121
|
+
| `E_DEP_INSTALL_FAILED` | template dependency install failed | CLI 0.5.6 templates use public npm SDK 3.0.0-beta.1. Check the project @howone scope points to https://registry.npmjs.org/ and retry bun install; do not ask for private registry credentials or repeat HowOne login. Older Apps retain their dependency/config: inspect their version evidence before migrating |
|
|
109
122
|
| `E_NETWORK` | transport failed | the CLI retries transient read/sync failures at most twice; if it still fails, inspect `details.codes`, proxy and VPN routing. `--insecure` only affects API TLS verification. Keep the existing App and query its state before repeating a mutation whose response was lost |
|
|
@@ -73,3 +73,10 @@ sandbox functions and pass the catalog to EAX. Plain AI generation does not requ
|
|
|
73
73
|
job: that command searches the published workflow catalog and can return 404 before promotion.
|
|
74
74
|
Then run `ai sync`, inspect the manifest, and `push`.
|
|
75
75
|
4. All of this happens in the edit session's draft, like schema changes: push soon after.
|
|
76
|
+
|
|
77
|
+
If AI authoring or execution reports `Token decryption failed`, or schema validation wraps a
|
|
78
|
+
failed Studio decrypt-key callback, check `howone whoami --json` against the same API origin.
|
|
79
|
+
If account verification succeeds, preserve the App and job state and report the downstream
|
|
80
|
+
error with its request/job ID for platform diagnosis. The CLI personal token and the
|
|
81
|
+
Studio-to-EAX credential are separate; do not substitute a private npm token, ask the user to
|
|
82
|
+
paste credentials, or repeatedly log in to repair a server-to-server token failure.
|
|
@@ -1,2 +1,2 @@
|
|
|
1
|
-
# HowOne SDK
|
|
2
|
-
@howone:registry=https://
|
|
1
|
+
# Download HowOne SDK from public npm; no private registry credentials are required.
|
|
2
|
+
@howone:registry=https://registry.npmjs.org/
|
package/templates/vite/AGENTS.md
CHANGED
|
@@ -9,7 +9,8 @@ Read this file once when entering the project, follow it during implementation,
|
|
|
9
9
|
- Package manager: `bun`
|
|
10
10
|
- Common commands: `bun run dev`, `bun run typecheck`, `bun run build`
|
|
11
11
|
- The scaffold normally installs dependencies during `howone init app`. If `node_modules` is missing, run `bun install` before validation instead of treating missing binaries as code failures.
|
|
12
|
-
- `@howone/sdk` uses
|
|
12
|
+
- `@howone/sdk@3.0.0-beta.1` uses public npm through the project's `.npmrc`; no private registry credentials are required. A package download error is separate from HowOne login.
|
|
13
|
+
- Cloud builds use the platform-managed private registry for the same SDK version. Keep local public registry configuration; do not copy cloud credentials into the project or change SDK versions to bypass a cloud download failure.
|
|
13
14
|
- Default stack: React, Vite, TypeScript, Tailwind CSS, shadcn/ui-style components, `@howone/sdk`
|
|
14
15
|
|
|
15
16
|
## Source of Truth
|