uniner-cli 1.0.10 → 1.0.12

package/README.md

@@ -61,6 +61,7 @@ uniner-cli --help
 uniner-cli web browser open --url "https://example.com"
 uniner-cli web element click --xpath "//button[@id='submit']"
 uniner-cli web element get-text --xpath "//h1"
+uniner-cli web action pdf --output report.pdf
 
 # Excel
 uniner-cli excel data read --file data.xlsx --cell A1
@@ -178,7 +179,15 @@ npm install -g uniner-cli
 
 ## Changelog
 
-### 1.1.0 (2026-07-05)
+### 1.0.11 (2026-07-16)
+
+- **feat**: 新增 `web action pdf` 命令，支持将当前网页导出为 PDF（纸张格式 / 横向 / 背景 / 页边距 / 页眉页脚 / 缩放 / 页面范围）。SDK 层新增 `chrome.pdf()` 方法。
+
+### 1.0.10 (2026-07-10)
+
+- **feat**: 优化 Windows 端用户体验
+
+### 1.0.9 (2026-07-05)
 
 - **feat**: SDK 1.24.0 同步 —— 新增 `tool ftp` 子命令（create-folder / check-folder / check-file / list-dir），跨平台可用
 - **feat**: `web browser close` 现在自动终止残留 chrome.exe 进程，避免进程泄漏

package/lib/SKILL.md.template

@@ -64,7 +64,7 @@ web                浏览器自动化（Playwright + CDP）
 ├── element        click / input / get-text / get-value / select / check / hover / screenshot
 ├── iframe         enter / exit / list
 ├── page           list / switch / close
-└── action         screenshot / execute-js / get-cookie / set-cookie
+└── action         screenshot / pdf / execute-js / get-cookie / set-cookie
 
 tool               通用工具
 ├── list           创建 / append / remove / find / sort / unique

package/package.json

@@ -1,6 +1,6 @@
 {
     "name":  "uniner-cli",
-    "version":  "1.0.10",
+    "version":  "1.0.12",
     "description":  "uniner-cli — RPA automation CLI: browser automation (Playwright/CDP), Excel, OCR, desktop/SAP, crypto/HTTP/email tools. Auto-installs a Claude Code skill on install.",
     "keywords":  [
                      "rpa",

package/scripts/cleanup.js

@@ -1,123 +1,123 @@
-// Shared cleanup logic for uninstall.
-// Extracted so both the npm lifecycle hook (preuninstall.js) and the
-// manual command (bin/uniner-cli-uninstall.js) can share it.
-
-'use strict';
-
-const fs   = require('fs');
-const path = require('path');
-
-const {
-    rootDir,
-    skillDir,
-    skillFile,
-} = require('../lib/paths');
-
-function rmRf(p) {
-    try {
-        if (fs.existsSync(p)) {
-            fs.rmSync(p, { recursive: true, force: true });
-            return true;
-        }
-        return false;
-    } catch (_) {
-        return false;
-    }
-}
-
-function rmFile(p) {
-    try {
-        if (fs.existsSync(p)) {
-            fs.unlinkSync(p);
-            return true;
-        }
-        return false;
-    } catch (_) {
-        return false;
-    }
-}
-
-/**
- * Run the full uninstall cleanup.
- *
- * @param {object}  [opts]
- * @param {boolean} [opts.verbose=false]  Print progress lines to stdout.
- *                                         The preuninstall hook should pass false
- *                                         because npm swallows lifecycle output
- *                                         unless --verbose is used; the manual
- *                                         command passes true so the user sees
- *                                         what happened.
- * @returns {{ didSomething: boolean, scenariosKept: number, scenariosDir: string|null }}
- */
-function cleanup(opts) {
-    const verbose = (opts && opts.verbose) || false;
-
-    function log(msg) {
-        if (verbose) {
-            console.log(`[uniner-cli] ${msg}`);
-        }
-    }
-
-    const root = rootDir();
-    let didSomething = false;
-
-    // 1. Remove the entire ~/.uniner-cli/ tree (all versions).
-    //    The version-specific layout exists so the installer can support
-    //    multi-version coexistence, but on uninstall the user wants a full
-    //    removal — orphaned old version dirs would just waste disk space.
-    if (rmRf(root)) {
-        log(`Removed ${root}`);
-        didSomething = true;
-    }
-
-    // 2. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir,
-    //    because the user's accumulated scenarios/<name>/ subdirectories
-    //    live there and represent real work they've sedimented over time.
-    const dir = skillDir();
-    if (rmFile(skillFile())) {
-        log(`Removed ${skillFile()}`);
-        didSomething = true;
-    }
-
-    // 3. Count scenarios/ subdirs that contain a meta.json.
-    let scenariosKept   = 0;
-    const scenariosPath = path.join(dir, 'scenarios');
-    if (fs.existsSync(scenariosPath)) {
-        try {
-            scenariosKept = fs.readdirSync(scenariosPath).filter(n => {
-                const meta = path.join(scenariosPath, n, 'meta.json');
-                return fs.existsSync(meta);
-            }).length;
-        } catch (_) {
-            // best-effort
-        }
-    }
-
-    // 4. If skill dir is now genuinely empty, remove it. Otherwise keep it.
-    try {
-        if (fs.existsSync(dir)) {
-            const remaining = fs.readdirSync(dir);
-            if (remaining.length === 0) {
-                fs.rmdirSync(dir);
-                log(`Removed empty ${dir}`);
-                didSomething = true;
-            } else if (verbose) {
-                log(`Keeping ${dir} (${scenariosKept} scenario(s) preserved)`);
-            }
-        }
-    } catch (_) {
-        // best-effort
-    }
-
-    if (!didSomething) {
-        log('Nothing to clean — already removed.');
-    }
-
-    return {
-        didSomething,
-        scenariosKept,
-        scenariosDir: scenariosKept > 0 ? scenariosPath : null,
-    };
-}
-
-module.exports = { cleanup };
+// Shared cleanup logic for uninstall.
+// Extracted so both the npm lifecycle hook (preuninstall.js) and the
+// manual command (bin/uniner-cli-uninstall.js) can share it.
+
+'use strict';
+
+const fs   = require('fs');
+const path = require('path');
+
+const {
+    rootDir,
+    skillDir,
+    skillFile,
+} = require('../lib/paths');
+
+function rmRf(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.rmSync(p, { recursive: true, force: true });
+            return true;
+        }
+        return false;
+    } catch (_) {
+        return false;
+    }
+}
+
+function rmFile(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.unlinkSync(p);
+            return true;
+        }
+        return false;
+    } catch (_) {
+        return false;
+    }
+}
+
+/**
+ * Run the full uninstall cleanup.
+ *
+ * @param {object}  [opts]
+ * @param {boolean} [opts.verbose=false]  Print progress lines to stdout.
+ *                                         The preuninstall hook should pass false
+ *                                         because npm swallows lifecycle output
+ *                                         unless --verbose is used; the manual
+ *                                         command passes true so the user sees
+ *                                         what happened.
+ * @returns {{ didSomething: boolean, scenariosKept: number, scenariosDir: string|null }}
+ */
+function cleanup(opts) {
+    const verbose = (opts && opts.verbose) || false;
+
+    function log(msg) {
+        if (verbose) {
+            console.log(`[uniner-cli] ${msg}`);
+        }
+    }
+
+    const root = rootDir();
+    let didSomething = false;
+
+    // 1. Remove the entire ~/.uniner-cli/ tree (all versions).
+    //    The version-specific layout exists so the installer can support
+    //    multi-version coexistence, but on uninstall the user wants a full
+    //    removal — orphaned old version dirs would just waste disk space.
+    if (rmRf(root)) {
+        log(`Removed ${root}`);
+        didSomething = true;
+    }
+
+    // 2. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir,
+    //    because the user's accumulated scenarios/<name>/ subdirectories
+    //    live there and represent real work they've sedimented over time.
+    const dir = skillDir();
+    if (rmFile(skillFile())) {
+        log(`Removed ${skillFile()}`);
+        didSomething = true;
+    }
+
+    // 3. Count scenarios/ subdirs that contain a meta.json.
+    let scenariosKept   = 0;
+    const scenariosPath = path.join(dir, 'scenarios');
+    if (fs.existsSync(scenariosPath)) {
+        try {
+            scenariosKept = fs.readdirSync(scenariosPath).filter(n => {
+                const meta = path.join(scenariosPath, n, 'meta.json');
+                return fs.existsSync(meta);
+            }).length;
+        } catch (_) {
+            // best-effort
+        }
+    }
+
+    // 4. If skill dir is now genuinely empty, remove it. Otherwise keep it.
+    try {
+        if (fs.existsSync(dir)) {
+            const remaining = fs.readdirSync(dir);
+            if (remaining.length === 0) {
+                fs.rmdirSync(dir);
+                log(`Removed empty ${dir}`);
+                didSomething = true;
+            } else if (verbose) {
+                log(`Keeping ${dir} (${scenariosKept} scenario(s) preserved)`);
+            }
+        }
+    } catch (_) {
+        // best-effort
+    }
+
+    if (!didSomething) {
+        log('Nothing to clean — already removed.');
+    }
+
+    return {
+        didSomething,
+        scenariosKept,
+        scenariosDir: scenariosKept > 0 ? scenariosPath : null,
+    };
+}
+
+module.exports = { cleanup };

package/scripts/preuninstall.js

@@ -1,25 +1,25 @@
-#!/usr/bin/env node
-// preuninstall.js — npm lifecycle hook, runs automatically on
-// `npm uninstall -g uniner-cli`.
-//
-// Cleans up the runtime tree (~/.uniner-cli/<version>/) and the skill file
-// (~/.claude/skills/uniner-cli/SKILL.md). Preserves user scenarios under
-// ~/.claude/skills/uniner-cli/scenarios/ — those represent accumulated
-// knowledge and are never deleted automatically.
-//
-// IMPORTANT: This script MUST exit 0 in all cases, otherwise it would
-// abort the user's `npm uninstall`. Errors are swallowed silently.
-//
-// The manual `uniner-cli-uninstall` command is still useful for users who
-// want verbose feedback, or who want to clean up before the npm package is
-// gone (e.g. if the hook somehow didn't fire).
-
-'use strict';
-
-const { cleanup } = require('./cleanup');
-
-try {
-    cleanup({ verbose: false });
-} catch (_) {
-    // Never fail the uninstall — swallow all errors.
-}
+#!/usr/bin/env node
+// preuninstall.js — npm lifecycle hook, runs automatically on
+// `npm uninstall -g uniner-cli`.
+//
+// Cleans up the runtime tree (~/.uniner-cli/<version>/) and the skill file
+// (~/.claude/skills/uniner-cli/SKILL.md). Preserves user scenarios under
+// ~/.claude/skills/uniner-cli/scenarios/ — those represent accumulated
+// knowledge and are never deleted automatically.
+//
+// IMPORTANT: This script MUST exit 0 in all cases, otherwise it would
+// abort the user's `npm uninstall`. Errors are swallowed silently.
+//
+// The manual `uniner-cli-uninstall` command is still useful for users who
+// want verbose feedback, or who want to clean up before the npm package is
+// gone (e.g. if the hook somehow didn't fire).
+
+'use strict';
+
+const { cleanup } = require('./cleanup');
+
+try {
+    cleanup({ verbose: false });
+} catch (_) {
+    // Never fail the uninstall — swallow all errors.
+}