@bsbofmusic/cdper-doubao 1.1.0 → 1.1.2

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
@@ -1,6 +1,6 @@
1
1
  # cdper-doubao
2
2
 
3
- Standalone Doubao CLI for controlling the user's real Chrome/Edge through CDP Bridge.
3
+ Standalone Doubao workflow CLI for the user's real logged-in Chrome over CDP. It is not a general browser automation framework; use official `playwright-core` directly for arbitrary page control after Chrome is available.
4
4
 
5
5
  ## Install
6
6
 
@@ -12,8 +12,7 @@ Requirements:
12
12
 
13
13
  - Node.js 18+
14
14
  - A real Chrome/Edge profile with Doubao logged in
15
- - Either local Chrome DevTools on `127.0.0.1:9222` or a remote CDP Bridge
16
- - Optional explicit CDP WS through `CDP_WS`, `~/.cdp-auth.json`, or `~/.cdp-bridge/config.json`
15
+ - Local Chrome DevTools on `127.0.0.1:9222` from your launcher/bridge; `CDP_WS` remains an optional explicit override
17
16
 
18
17
  ## Use
19
18
 
@@ -67,4 +66,4 @@ Design note: Doubao link reading is more reliable when URLs are included in the
67
66
  ---
68
67
  ## Security
69
68
 
70
- All browser control happens through the user's real browser via local CDP or CDP Bridge. Tokens are redacted from diagnostic output. Do not commit `CDP_WS` or full WebSocket URLs containing `token=`.
69
+ All Doubao workflow control happens through the user's real browser via local CDP. Tokens are redacted from diagnostic output. Do not commit `CDP_WS` or full WebSocket URLs containing `token=`. For arbitrary page automation, use `playwright-core` directly instead of expanding cdper's product surface.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@bsbofmusic/cdper-doubao",
3
- "version": "1.1.0",
3
+ "version": "1.1.2",
4
4
  "description": "Standalone Doubao CLI controlled through a user's real Chrome/Edge via CDP Bridge",
5
5
  "type": "commonjs",
6
6
  "main": "src/public-api.js",
@@ -22,7 +22,8 @@
22
22
  },
23
23
  "files": [
24
24
  "manifest.json",
25
- "src/",
25
+ "src/**/*.js",
26
+ "src/**/*.d.ts",
26
27
  "bin/cdper-doubao.cjs"
27
28
  ],
28
29
  "keywords": [
@@ -48,7 +49,7 @@
48
49
  "node": ">=18.0.0"
49
50
  },
50
51
  "dependencies": {
51
- "@bsbofmusic/cdper-core": "~1.3.0",
52
+ "@bsbofmusic/cdper-core": "~1.3.3",
52
53
  "yargs": "^17.7.2"
53
54
  }
54
55
  }
package/src/public-api.js CHANGED
@@ -1,16 +1,21 @@
1
+ "use strict";
2
+ Object.defineProperty(exports, "__esModule", { value: true });
3
+ exports.queryDoubao = exports.manifest = void 0;
4
+ exports.getCapabilities = getCapabilities;
1
5
  const manifest = require('../manifest.json');
6
+ exports.manifest = manifest;
2
7
  const { queryDoubao } = require('./doubao.js');
3
-
8
+ exports.queryDoubao = queryDoubao;
4
9
  function getCapabilities() {
5
- return (manifest.capabilities?.provides || []).map((id) => ({
6
- id,
7
- version: '1.0',
8
- summary: id,
9
- }));
10
+ const typedManifest = manifest;
11
+ return (typedManifest.capabilities?.provides || []).map((id) => ({
12
+ id,
13
+ version: '1.0',
14
+ summary: id,
15
+ }));
10
16
  }
11
-
12
17
  module.exports = {
13
- manifest,
14
- getCapabilities,
15
- queryDoubao,
18
+ manifest,
19
+ getCapabilities,
20
+ queryDoubao,
16
21
  };