@skrillex1224/chrome-apify-fleet-extension 1.0.39 → 1.0.40
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/package.json +1 -1
- package/release-guide.js +1 -1
- package/release-guide.md +2 -2
- package/release-guide.mjs +1 -1
- package/release-meta.js +5 -5
- package/release-meta.json +5 -5
- package/release-meta.mjs +5 -5
package/package.json
CHANGED
package/release-guide.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
module.exports = "# Fleet Commander Toolbox 安装说明\n\n适用范围：内部环境采集扩展。插件只读取浏览器 Cookie/Storage/浏览器观测值并回传后台。\n\n## 快速安装（开发者模式）\n\n步骤 1：下载插件 ZIP \n下载地址：[https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.
|
|
1
|
+
module.exports = "# Fleet Commander Toolbox 安装说明\n\n适用范围：内部环境采集扩展。插件只读取浏览器 Cookie/Storage/浏览器观测值并回传后台。\n\n## 快速安装（开发者模式）\n\n步骤 1：下载插件 ZIP \n下载地址：[https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.40.zip](https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.40.zip) \n版本号：1.0.40\n\n步骤 2：解压 ZIP \n解压后会得到一个包含 `manifest.json` 的文件夹。\n\n步骤 3：打开扩展管理页 \n打开：[chrome://extensions](chrome://extensions)\n\n步骤 4：开启开发者模式 \n在页面右上角打开「开发者模式」开关。\n\n步骤 5：加载已解压扩展 \n点击「加载已解压的扩展程序」，选择刚刚解压的目录。\n\n## 使用方式\n\n步骤 1：打开目标站点并完成登录（登录后标签页可关闭，扩展会自动打开读取）。 \n步骤 2：进入管理后台环境导入页，切换到对应的平台，点击「从活跃标签页自动读取」。 \n步骤 3：扩展会自动回传当前站点的 Cookie/LocalStorage/SessionStorage/浏览器观测值，提交后会清理 Cookies/Storage 并关闭该域名的所有标签页。 \n如需手动退出登录，可在扩展弹窗中点击「清空当前页面登录态」，会清理 Cookies/Storage 并刷新页面。\n\n## 更新\n\n重新下载最新 ZIP（文件名包含版本号），解压后在 [chrome://extensions](chrome://extensions) 里移除旧扩展并重新加载即可。\n\n## 卸载\n\n在 [chrome://extensions](chrome://extensions) 中移除扩展即可。\n\n## 调试日志（可选）\n\n如果需要查看扩展读取/清理的域名与来源，可以在控制台执行：\n\n```js\nchrome.storage.local.set({ fleet_debug_logs: true });\n```\n\n关闭调试日志：\n\n```js\nchrome.storage.local.set({ fleet_debug_logs: false });\n```\n";
|
package/release-guide.md
CHANGED
|
@@ -5,8 +5,8 @@
|
|
|
5
5
|
## 快速安装（开发者模式）
|
|
6
6
|
|
|
7
7
|
步骤 1：下载插件 ZIP
|
|
8
|
-
下载地址：[https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.
|
|
9
|
-
版本号：1.0.
|
|
8
|
+
下载地址：[https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.40.zip](https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.40.zip)
|
|
9
|
+
版本号：1.0.40
|
|
10
10
|
|
|
11
11
|
步骤 2：解压 ZIP
|
|
12
12
|
解压后会得到一个包含 `manifest.json` 的文件夹。
|
package/release-guide.mjs
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
|
-
const releaseGuide = "# Fleet Commander Toolbox 安装说明\n\n适用范围：内部环境采集扩展。插件只读取浏览器 Cookie/Storage/浏览器观测值并回传后台。\n\n## 快速安装（开发者模式）\n\n步骤 1：下载插件 ZIP \n下载地址：[https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.
|
|
1
|
+
const releaseGuide = "# Fleet Commander Toolbox 安装说明\n\n适用范围：内部环境采集扩展。插件只读取浏览器 Cookie/Storage/浏览器观测值并回传后台。\n\n## 快速安装（开发者模式）\n\n步骤 1：下载插件 ZIP \n下载地址：[https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.40.zip](https://heartbitai.com/fleet/extensions/fleet-commander-toolbox-1.0.40.zip) \n版本号：1.0.40\n\n步骤 2：解压 ZIP \n解压后会得到一个包含 `manifest.json` 的文件夹。\n\n步骤 3：打开扩展管理页 \n打开：[chrome://extensions](chrome://extensions)\n\n步骤 4：开启开发者模式 \n在页面右上角打开「开发者模式」开关。\n\n步骤 5：加载已解压扩展 \n点击「加载已解压的扩展程序」，选择刚刚解压的目录。\n\n## 使用方式\n\n步骤 1：打开目标站点并完成登录（登录后标签页可关闭，扩展会自动打开读取）。 \n步骤 2：进入管理后台环境导入页，切换到对应的平台，点击「从活跃标签页自动读取」。 \n步骤 3：扩展会自动回传当前站点的 Cookie/LocalStorage/SessionStorage/浏览器观测值，提交后会清理 Cookies/Storage 并关闭该域名的所有标签页。 \n如需手动退出登录，可在扩展弹窗中点击「清空当前页面登录态」，会清理 Cookies/Storage 并刷新页面。\n\n## 更新\n\n重新下载最新 ZIP（文件名包含版本号），解压后在 [chrome://extensions](chrome://extensions) 里移除旧扩展并重新加载即可。\n\n## 卸载\n\n在 [chrome://extensions](chrome://extensions) 中移除扩展即可。\n\n## 调试日志（可选）\n\n如果需要查看扩展读取/清理的域名与来源，可以在控制台执行：\n\n```js\nchrome.storage.local.set({ fleet_debug_logs: true });\n```\n\n关闭调试日志：\n\n```js\nchrome.storage.local.set({ fleet_debug_logs: false });\n```\n";
|
|
2
2
|
export default releaseGuide;
|
package/release-meta.js
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
module.exports = {
|
|
2
|
-
"version": "1.0.
|
|
3
|
-
"zipName": "fleet-commander-toolbox-1.0.
|
|
4
|
-
"path": "/fleet/extensions/fleet-commander-toolbox-1.0.
|
|
5
|
-
"updatedAt": "2026-03-17T07:
|
|
6
|
-
"updated_at": "2026-03-17T07:
|
|
2
|
+
"version": "1.0.40",
|
|
3
|
+
"zipName": "fleet-commander-toolbox-1.0.40.zip",
|
|
4
|
+
"path": "/fleet/extensions/fleet-commander-toolbox-1.0.40.zip",
|
|
5
|
+
"updatedAt": "2026-03-17T07:36:15.447Z",
|
|
6
|
+
"updated_at": "2026-03-17T07:36:15.447Z"
|
|
7
7
|
};
|
package/release-meta.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
|
-
"version": "1.0.
|
|
3
|
-
"zipName": "fleet-commander-toolbox-1.0.
|
|
4
|
-
"path": "/fleet/extensions/fleet-commander-toolbox-1.0.
|
|
5
|
-
"updatedAt": "2026-03-17T07:
|
|
6
|
-
"updated_at": "2026-03-17T07:
|
|
2
|
+
"version": "1.0.40",
|
|
3
|
+
"zipName": "fleet-commander-toolbox-1.0.40.zip",
|
|
4
|
+
"path": "/fleet/extensions/fleet-commander-toolbox-1.0.40.zip",
|
|
5
|
+
"updatedAt": "2026-03-17T07:36:15.447Z",
|
|
6
|
+
"updated_at": "2026-03-17T07:36:15.447Z"
|
|
7
7
|
}
|
package/release-meta.mjs
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
const releaseMeta = {
|
|
2
|
-
"version": "1.0.
|
|
3
|
-
"zipName": "fleet-commander-toolbox-1.0.
|
|
4
|
-
"path": "/fleet/extensions/fleet-commander-toolbox-1.0.
|
|
5
|
-
"updatedAt": "2026-03-17T07:
|
|
6
|
-
"updated_at": "2026-03-17T07:
|
|
2
|
+
"version": "1.0.40",
|
|
3
|
+
"zipName": "fleet-commander-toolbox-1.0.40.zip",
|
|
4
|
+
"path": "/fleet/extensions/fleet-commander-toolbox-1.0.40.zip",
|
|
5
|
+
"updatedAt": "2026-03-17T07:36:15.447Z",
|
|
6
|
+
"updated_at": "2026-03-17T07:36:15.447Z"
|
|
7
7
|
};
|
|
8
8
|
export default releaseMeta;
|