@hubspot/cli 8.16.0 → 8.17.0-beta.1
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/bin/cli.js +19 -1
- package/commands/cms/lighthouseScore.js +1 -1
- package/commands/mcp/setup.d.ts +1 -0
- package/commands/mcp/setup.js +8 -1
- package/commands/project/download.d.ts +2 -0
- package/commands/project/download.js +56 -16
- package/lang/en.d.ts +61 -6
- package/lang/en.js +168 -11
- package/lib/agentHelp.d.ts +17 -0
- package/lib/agentHelp.js +90 -0
- package/lib/app/migrate.js +2 -5
- package/lib/commonOpts.js +4 -0
- package/lib/jsonOutput/projectDownload.d.ts +1 -0
- package/lib/jsonOutput/projectDownload.js +1 -0
- package/lib/mcp/clients.d.ts +2 -1
- package/lib/mcp/clients.js +7 -7
- package/lib/mcp/setup.d.ts +1 -1
- package/lib/mcp/setup.js +21 -36
- package/lib/mcp/skills.d.ts +8 -0
- package/lib/mcp/skills.js +64 -0
- package/lib/projects/archive.d.ts +8 -0
- package/lib/projects/archive.js +104 -0
- package/lib/projects/archiveDiff.d.ts +12 -0
- package/lib/projects/archiveDiff.js +68 -0
- package/lib/projects/config.js +1 -1
- package/lib/projects/download.d.ts +37 -0
- package/lib/projects/download.js +123 -0
- package/lib/projects/localDev/LocalDevWatcher.js +2 -1
- package/lib/prompts/importDataTestAccountSelectPrompt.js +1 -1
- package/lib/validation.js +16 -1
- package/lib/yargs/makeWrappedYargsHandler.d.ts +1 -0
- package/lib/yargs/makeWrappedYargsHandler.js +7 -0
- package/mcp-server/skills/hubspot-fix-build/SKILL.md +61 -0
- package/mcp-server/skills/hubspot-new-app/SKILL.md +84 -0
- package/mcp-server/tools/project/DocFetchTool.d.ts +4 -1
- package/mcp-server/tools/project/DocFetchTool.js +52 -7
- package/mcp-server/tools/project/FindProjectsTool.js +4 -1
- package/mcp-server/tools/project/GetBuildLogsTool.d.ts +1 -1
- package/package.json +6 -8
|
@@ -0,0 +1,61 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: hubspot-fix-build
|
|
3
|
+
description: Diagnose and fix a failed HubSpot project build with the HubSpot CLI MCP tools. Use when a HubSpot project build failed, an `hs project upload` or `upload-project` failed, or a project deploy is blocked by a build error. Do not use it for other builds, such as npm, CI, or local compiler builds. Also use when `upload-project` returns a build failure. The skill finds the cause, fixes the project files, and asks before it uploads again.
|
|
4
|
+
disable-model-invocation: false
|
|
5
|
+
allowed-tools: Read, Grep, Glob
|
|
6
|
+
argument-hint: '[project-path] [build-id]'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Fix a failed HubSpot project build
|
|
10
|
+
|
|
11
|
+
Use this skill to find why a build failed and to fix it. Work from the error text. Do not guess a cause.
|
|
12
|
+
|
|
13
|
+
The tools in this skill come from the HubSpot CLI MCP server, which `hs mcp setup` adds as `HubSpotDev`. If more than one server has a tool with the same name, use the one from `HubSpotDev`.
|
|
14
|
+
|
|
15
|
+
## Task
|
|
16
|
+
|
|
17
|
+
When this skill is invoked:
|
|
18
|
+
|
|
19
|
+
### 1. Locate the project
|
|
20
|
+
|
|
21
|
+
`get-build-status` and `get-build-logs` need the project path, even when you have a build ID. Find the project before you look at any build.
|
|
22
|
+
|
|
23
|
+
1. If the user passed a project path as an argument, use it.
|
|
24
|
+
2. Otherwise call `find-projects`. If it finds several projects, ask the user which one to use.
|
|
25
|
+
3. If the user passed a build ID, keep it for step 2. A build ID does not tell you which project it belongs to.
|
|
26
|
+
|
|
27
|
+
### 2. Find the failed build
|
|
28
|
+
|
|
29
|
+
1. Call `get-build-status` with no `buildId`. It shows the recent builds.
|
|
30
|
+
2. If the user named a build, use that build. Otherwise use the latest build with a failure status.
|
|
31
|
+
3. Call `get-build-status` again with that `buildId`. Read `buildErrorMessage` and the failed subbuilds.
|
|
32
|
+
|
|
33
|
+
If the latest build succeeded, tell the user. Ask which build they mean.
|
|
34
|
+
|
|
35
|
+
### 3. Read the logs only if needed
|
|
36
|
+
|
|
37
|
+
The status output often has enough detail. Call `get-build-logs` in these cases:
|
|
38
|
+
|
|
39
|
+
- The error message is vague or empty.
|
|
40
|
+
- The user asks about warnings.
|
|
41
|
+
- The subbuild failure does not name a file or a field.
|
|
42
|
+
|
|
43
|
+
Start with `logLevel` set to `ERROR`. Use `WARN` for warnings. Use `ALL` as the last choice.
|
|
44
|
+
|
|
45
|
+
### 4. Fix the cause
|
|
46
|
+
|
|
47
|
+
1. Name the cause to the user in one or two sentences. Quote the error text.
|
|
48
|
+
2. If the error points to a `*-hsmeta.json` file, read `platformVersion` in `hsproject.json`. Call `get-feature-config-schema` with that version and the `type` field from the file. Fix the file with values the schema allows.
|
|
49
|
+
3. For other errors, fix the named file.
|
|
50
|
+
4. Do not change `distribution` or `auth` in `app-hsmeta.json` to clear an error. These values cannot change after the first upload. Tell the user and ask what they want to do.
|
|
51
|
+
5. If you cannot find the cause, show the error text to the user without changes. Say which files and logs you read.
|
|
52
|
+
|
|
53
|
+
### 5. Validate
|
|
54
|
+
|
|
55
|
+
Call `validate-project`. Fix each error and call it again. Repeat until it passes.
|
|
56
|
+
|
|
57
|
+
### 6. Ask before you upload
|
|
58
|
+
|
|
59
|
+
Say what you changed. Ask the user whether to upload again. If they say yes, call `upload-project`. If the project uses profiles, ask the user which profile to use. Never choose a profile yourself.
|
|
60
|
+
|
|
61
|
+
After the upload, call `get-build-status` to read the status of the new build. If it fails again, go back to step 2. If the same error repeats after two fixes, stop and show the user the error and what you tried.
|
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: hubspot-new-app
|
|
3
|
+
description: Plan and create a HubSpot developer-platform app project with the HubSpot CLI MCP tools. Use when the user wants to build, start, or scaffold a HubSpot developer-platform app project (an `hsproject.json` project). Also use when the user wants to add features such as cards, webhooks, workflow actions, or app functions to a project. Also use when the user has only a rough idea and needs help to choose features, distribution, and auth type. The skill ends with a local project that passes validation. It does not upload or deploy.
|
|
4
|
+
disable-model-invocation: false
|
|
5
|
+
allowed-tools: Read, Grep, Glob
|
|
6
|
+
argument-hint: '[app-idea]'
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Plan and create a HubSpot app project
|
|
10
|
+
|
|
11
|
+
Use this skill to turn an idea into a local HubSpot project that passes validation. The first upload fixes two choices: distribution and auth type. A wrong choice means a new project, so plan before you scaffold.
|
|
12
|
+
|
|
13
|
+
Never choose distribution, auth type, project name, or destination for the user. Ask.
|
|
14
|
+
|
|
15
|
+
The tools in this skill come from the HubSpot CLI MCP server, which `hs mcp setup` adds as `HubSpotDev`. If more than one server has a tool with the same name, use the one from `HubSpotDev`.
|
|
16
|
+
|
|
17
|
+
## Task
|
|
18
|
+
|
|
19
|
+
When this skill is invoked:
|
|
20
|
+
|
|
21
|
+
### 1. Find the starting point
|
|
22
|
+
|
|
23
|
+
1. If the user wants to add features to an existing project, call `find-projects` on the working directory, then skip to step 4 and use `add-feature-to-project`. If the user wants a new app, do not call `find-projects`. If you cannot tell which one the user wants, ask.
|
|
24
|
+
2. If any tool reports "No account ID found", or no account is authenticated, call `auth-account`. Tell the user that a browser tab opens and that they must click "Connect to CLI". Then retry the blocked step.
|
|
25
|
+
3. If the user wants a safe place to test, offer `create-test-account`. Follow that tool's own workflow: look for a test account config file, show it to the user, and ask before you use it. If there is no file, ask for the account name and the tier for each hub.
|
|
26
|
+
|
|
27
|
+
### 2. Plan
|
|
28
|
+
|
|
29
|
+
If the user already stated what the app does, the features, the distribution, and the auth type, skip this step.
|
|
30
|
+
|
|
31
|
+
1. If the user passed an app idea as an argument (for example `/hubspot-new-app a card that shows open tickets`), use it. Otherwise ask one question: what must the app do for its users?
|
|
32
|
+
2. Call `search-docs` for that goal. Call `fetch-doc` on the best results. Choose features from the docs. The valid feature values are:
|
|
33
|
+
|
|
34
|
+
```
|
|
35
|
+
card, settings, app-function, app-function-endpoint, webhooks,
|
|
36
|
+
workflow-action, workflow-action-tool, app-object, app-event,
|
|
37
|
+
scim, page, crm-bulk-action
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
3. Keep these features apart:
|
|
41
|
+
- `app-function` is a private serverless function inside the app.
|
|
42
|
+
- `app-function-endpoint` is an app serverless function with a public endpoint.
|
|
43
|
+
- `workflow-action-tool` is an agent tool.
|
|
44
|
+
- Do not confuse any of them with a CMS serverless function. That is a different product.
|
|
45
|
+
4. If a fetched doc has a "Supported products" section, tell the user the required product and tier in plain words. For example: "This feature requires Content Hub Enterprise." Do this before you scaffold. If no fetched doc has that section, do not state a tier.
|
|
46
|
+
5. Ask for the distribution:
|
|
47
|
+
- `private`: the app is not listed on the HubSpot marketplace.
|
|
48
|
+
- `marketplace`: the app is listed on the HubSpot marketplace.
|
|
49
|
+
6. Ask for the auth type. `oauth` works for both distributions. `static` works only with `private` distribution.
|
|
50
|
+
7. Ask for the project name. Ask for the destination directory. The destination becomes the project folder itself, so use the exact path that the user gives. Do not use the current directory unless the user says so.
|
|
51
|
+
8. After the user answers, show the full plan: name, destination, project base (`app` or `empty`), distribution, auth type, and features.
|
|
52
|
+
9. Ask "Create this project?" Say that distribution and auth type cannot change after the first upload. Wait for a yes in a separate reply. Answers to your questions are not a yes. Do not call `create-project` or `add-feature-to-project` before the yes.
|
|
53
|
+
|
|
54
|
+
### 3. Create a new project
|
|
55
|
+
|
|
56
|
+
Call `create-project` with every value from the plan:
|
|
57
|
+
|
|
58
|
+
- `name`, `destination`
|
|
59
|
+
- `projectBase`: `app` for a project with an app, `empty` for a project without one
|
|
60
|
+
- `distribution` and `auth` (for base `app` only)
|
|
61
|
+
- `features`
|
|
62
|
+
|
|
63
|
+
If the tool answers with a question, ask the user. Do not guess a value.
|
|
64
|
+
|
|
65
|
+
### 4. Add features to an existing project
|
|
66
|
+
|
|
67
|
+
Call `add-feature-to-project` with `absoluteProjectPath` and `features`.
|
|
68
|
+
|
|
69
|
+
- If the project has no app, set `addApp` to `true`. A project needs an app before it can hold a feature.
|
|
70
|
+
- When `addApp` is `true`, pass `distribution` and `auth`. Ask the user for them, as in step 2. Otherwise omit them.
|
|
71
|
+
|
|
72
|
+
### 5. Configure and validate
|
|
73
|
+
|
|
74
|
+
1. Open `hsproject.json` and read `platformVersion`.
|
|
75
|
+
2. Before you edit any `*-hsmeta.json` file, call `get-feature-config-schema` with that `platformVersion` and the `type` field from the file. Use only the values the schema allows.
|
|
76
|
+
3. Edit the file.
|
|
77
|
+
4. If a feature reads or writes CRM data, add the scopes it needs to `requiredScopes` in `app-hsmeta.json`. The schema does not list scope names, so find the exact names with `search-docs` and `fetch-doc`.
|
|
78
|
+
5. Call `validate-project`. Fix each error and call it again. Repeat until it passes. If you cannot fix an error, show the error text to the user without changes.
|
|
79
|
+
|
|
80
|
+
### 6. Finish
|
|
81
|
+
|
|
82
|
+
Tell the user which files you created and which features the project has. Tell them that the project is ready to upload, and that the first upload makes distribution and auth type permanent.
|
|
83
|
+
|
|
84
|
+
Do not call `upload-project` in this skill. Stop here. If the user asks to upload later, treat it as a new request. If that build fails, use the `hubspot-fix-build` skill.
|
|
@@ -6,11 +6,14 @@ import { Tool } from '../../Tool.js';
|
|
|
6
6
|
declare const inputSchemaZodObject: z.ZodObject<{
|
|
7
7
|
docUrl: z.ZodString;
|
|
8
8
|
absoluteCurrentWorkingDirectory: z.ZodString;
|
|
9
|
+
offset: z.ZodDefault<z.ZodNumber>;
|
|
10
|
+
maxCharacters: z.ZodDefault<z.ZodNumber>;
|
|
11
|
+
fullDocument: z.ZodDefault<z.ZodBoolean>;
|
|
9
12
|
}, z.z.core.$strip>;
|
|
10
13
|
type InputSchemaType = z.infer<typeof inputSchemaZodObject>;
|
|
11
14
|
export declare class DocFetchTool extends Tool<InputSchemaType> {
|
|
12
15
|
constructor(mcpServer: McpServer, logger: McpLogger);
|
|
13
|
-
handler({ docUrl, absoluteCurrentWorkingDirectory, }: InputSchemaType): Promise<McpToolResponse>;
|
|
16
|
+
handler({ docUrl, absoluteCurrentWorkingDirectory, offset, maxCharacters, fullDocument, }: InputSchemaType): Promise<McpToolResponse>;
|
|
14
17
|
register(): RegisteredTool;
|
|
15
18
|
}
|
|
16
19
|
export {};
|
|
@@ -1,14 +1,40 @@
|
|
|
1
1
|
import z from 'zod';
|
|
2
2
|
import { Tool } from '../../Tool.js';
|
|
3
|
-
import { formatTextContents } from '../../utils/content.js';
|
|
3
|
+
import { formatErrorTextContents, formatTextContents, } from '../../utils/content.js';
|
|
4
4
|
import { absoluteCurrentWorkingDirectory, docUrl } from './constants.js';
|
|
5
5
|
import { http } from '@hubspot/local-dev-lib/http/unauthed';
|
|
6
6
|
import { isHubSpotHttpError } from '@hubspot/local-dev-lib/errors/index';
|
|
7
7
|
import { setupHubSpotConfig } from '../../utils/config.js';
|
|
8
8
|
import { getErrorMessage } from '../../../lib/errorHandlers/index.js';
|
|
9
|
+
const offset = z
|
|
10
|
+
.number()
|
|
11
|
+
.int()
|
|
12
|
+
.min(0)
|
|
13
|
+
.default(0)
|
|
14
|
+
.describe('The character position to start reading from. When more content is available, the response gives the offset for the next part.');
|
|
15
|
+
const maxCharacters = z
|
|
16
|
+
.number()
|
|
17
|
+
.int()
|
|
18
|
+
.min(1000)
|
|
19
|
+
.max(40000)
|
|
20
|
+
.default(20000)
|
|
21
|
+
.describe('The maximum number of characters to return.');
|
|
22
|
+
const fullDocument = z
|
|
23
|
+
.boolean()
|
|
24
|
+
.default(false)
|
|
25
|
+
.describe('Set to true to return the whole document with no character limit. This ignores offset and maxCharacters. Set this only when the user asks for the whole page.');
|
|
9
26
|
const inputSchema = {
|
|
10
27
|
docUrl,
|
|
11
28
|
absoluteCurrentWorkingDirectory,
|
|
29
|
+
offset,
|
|
30
|
+
maxCharacters,
|
|
31
|
+
fullDocument,
|
|
32
|
+
};
|
|
33
|
+
const outputSchema = {
|
|
34
|
+
text: z.string(),
|
|
35
|
+
offset: z.number(),
|
|
36
|
+
nextOffset: z.number().optional(),
|
|
37
|
+
totalCharacters: z.number(),
|
|
12
38
|
};
|
|
13
39
|
// eslint-disable-next-line @typescript-eslint/no-unused-vars
|
|
14
40
|
const inputSchemaZodObject = z.object({
|
|
@@ -19,7 +45,7 @@ export class DocFetchTool extends Tool {
|
|
|
19
45
|
constructor(mcpServer, logger) {
|
|
20
46
|
super(mcpServer, logger, toolName);
|
|
21
47
|
}
|
|
22
|
-
async handler({ docUrl, absoluteCurrentWorkingDirectory, }) {
|
|
48
|
+
async handler({ docUrl, absoluteCurrentWorkingDirectory, offset, maxCharacters, fullDocument, }) {
|
|
23
49
|
setupHubSpotConfig(absoluteCurrentWorkingDirectory);
|
|
24
50
|
try {
|
|
25
51
|
// Append .md extension to the URL
|
|
@@ -29,9 +55,27 @@ export class DocFetchTool extends Tool {
|
|
|
29
55
|
});
|
|
30
56
|
const content = response.data;
|
|
31
57
|
if (!content || content.trim().length === 0) {
|
|
32
|
-
return
|
|
58
|
+
return formatErrorTextContents('Document is empty or contains no content.');
|
|
59
|
+
}
|
|
60
|
+
if (!fullDocument && offset >= content.length) {
|
|
61
|
+
return formatErrorTextContents(`Offset ${offset} is past the end of the document, which has ${content.length} characters.`);
|
|
33
62
|
}
|
|
34
|
-
|
|
63
|
+
const start = fullDocument ? 0 : offset;
|
|
64
|
+
const chunkEnd = fullDocument
|
|
65
|
+
? content.length
|
|
66
|
+
: Math.min(offset + maxCharacters, content.length);
|
|
67
|
+
const nextOffset = chunkEnd < content.length ? chunkEnd : undefined;
|
|
68
|
+
const text = content.slice(start, chunkEnd);
|
|
69
|
+
const result = await formatTextContents(text, nextOffset === undefined
|
|
70
|
+
? undefined
|
|
71
|
+
: `This is part of the document (characters ${start} to ${chunkEnd} of ${content.length}). More content is available. To read the next part, call ${toolName} again with the same arguments and offset set to ${nextOffset}.`);
|
|
72
|
+
result.structuredContent = {
|
|
73
|
+
text,
|
|
74
|
+
offset: start,
|
|
75
|
+
nextOffset,
|
|
76
|
+
totalCharacters: content.length,
|
|
77
|
+
};
|
|
78
|
+
return result;
|
|
35
79
|
}
|
|
36
80
|
catch (error) {
|
|
37
81
|
this.logger.debug(toolName, {
|
|
@@ -39,17 +83,18 @@ export class DocFetchTool extends Tool {
|
|
|
39
83
|
error: error instanceof Error ? error.message : String(error),
|
|
40
84
|
});
|
|
41
85
|
if (isHubSpotHttpError(error)) {
|
|
42
|
-
return
|
|
86
|
+
return formatErrorTextContents(error.toString());
|
|
43
87
|
}
|
|
44
88
|
const errorMessage = `Error fetching documentation: ${getErrorMessage(error)}`;
|
|
45
|
-
return
|
|
89
|
+
return formatErrorTextContents(errorMessage);
|
|
46
90
|
}
|
|
47
91
|
}
|
|
48
92
|
register() {
|
|
49
93
|
return this.mcpServer.registerTool(toolName, {
|
|
50
94
|
title: 'Fetch HubSpot Developer Documentation (single file)',
|
|
51
|
-
description: 'Always use this immediately after `search-docs` and before creating a plan, writing code, or answering technical questions. This tool retrieves the
|
|
95
|
+
description: 'Always use this immediately after `search-docs` and before creating a plan, writing code, or answering technical questions. This tool retrieves the authoritative content of a HubSpot Developer Documentation page from its URL, ensuring responses are accurate, up-to-date, and grounded in the official docs. Long pages return in parts. The response says when more content is available and how to fetch the next part. Some pages include a "Supported products" section (a `<SupportedProducts .../>` tag) listing the products and subscription tiers a feature requires. Read it to tell the user whether a feature is available on their plan, stated plainly (for example "requires Content Hub Enterprise") rather than by quoting raw spec fields.',
|
|
52
96
|
inputSchema,
|
|
97
|
+
outputSchema,
|
|
53
98
|
annotations: {
|
|
54
99
|
readOnlyHint: true,
|
|
55
100
|
openWorldHint: true,
|
|
@@ -30,7 +30,10 @@ export class FindProjectsTool extends Tool {
|
|
|
30
30
|
const selected = await elicitSelection(this.mcpServer, this.logger, {
|
|
31
31
|
message: 'Select the HubSpot project to use.',
|
|
32
32
|
title: 'HubSpot project',
|
|
33
|
-
options: projectDirs.map(dir => ({
|
|
33
|
+
options: projectDirs.map(dir => ({
|
|
34
|
+
value: dir,
|
|
35
|
+
label: path.relative(absoluteDirectory, dir) || '.',
|
|
36
|
+
})),
|
|
34
37
|
});
|
|
35
38
|
if (selected) {
|
|
36
39
|
return formatTextContents(`Selected project: ${selected}`);
|
|
@@ -10,9 +10,9 @@ declare const inputSchemaZodObject: z.ZodObject<{
|
|
|
10
10
|
buildId: z.ZodNumber;
|
|
11
11
|
logLevel: z.ZodOptional<z.ZodEnum<{
|
|
12
12
|
ERROR: "ERROR";
|
|
13
|
+
ALL: "ALL";
|
|
13
14
|
WARN: "WARN";
|
|
14
15
|
INFO: "INFO";
|
|
15
|
-
ALL: "ALL";
|
|
16
16
|
}>>;
|
|
17
17
|
}, z.core.$strip>;
|
|
18
18
|
export type GetBuildLogsInputSchema = z.infer<typeof inputSchemaZodObject>;
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@hubspot/cli",
|
|
3
|
-
"version": "8.
|
|
3
|
+
"version": "8.17.0-beta.1",
|
|
4
4
|
"description": "The official CLI for developing on HubSpot",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": "https://github.com/HubSpot/hubspot-cli",
|
|
@@ -10,18 +10,17 @@
|
|
|
10
10
|
"!**/__tests__/**"
|
|
11
11
|
],
|
|
12
12
|
"dependencies": {
|
|
13
|
-
"@hubspot/local-dev-lib": "5.
|
|
14
|
-
"@hubspot/project-parsing-lib": "0.23.
|
|
13
|
+
"@hubspot/local-dev-lib": "5.14.0",
|
|
14
|
+
"@hubspot/project-parsing-lib": "0.23.7",
|
|
15
15
|
"@hubspot/ui-extensions-dev-server": "2.2.2",
|
|
16
16
|
"@inquirer/prompts": "7.10.1",
|
|
17
|
-
"@modelcontextprotocol/sdk": "1.
|
|
17
|
+
"@modelcontextprotocol/sdk": "1.32.1",
|
|
18
18
|
"archiver": "7.0.1",
|
|
19
19
|
"chalk": "5.6.2",
|
|
20
|
-
"chokidar": "
|
|
20
|
+
"chokidar": "4.0.3",
|
|
21
21
|
"cli-cursor": "3.1.0",
|
|
22
22
|
"cli-progress": "3.12.0",
|
|
23
23
|
"express": "4.22.3",
|
|
24
|
-
"findup-sync": "4.0.0",
|
|
25
24
|
"fs-extra": "8.1.0",
|
|
26
25
|
"ink": "6.8.0",
|
|
27
26
|
"ink-spinner": "5.0.0",
|
|
@@ -37,7 +36,7 @@
|
|
|
37
36
|
"table": "6.9.0",
|
|
38
37
|
"tmp": "0.2.7",
|
|
39
38
|
"update-notifier": "7.3.1",
|
|
40
|
-
"ws": "8.
|
|
39
|
+
"ws": "8.22.0",
|
|
41
40
|
"yargs": "17.7.3",
|
|
42
41
|
"yargs-parser": "21.1.1",
|
|
43
42
|
"zod": "^4.4.3"
|
|
@@ -47,7 +46,6 @@
|
|
|
47
46
|
"@types/archiver": "^6.0.3",
|
|
48
47
|
"@types/cli-progress": "^3.11.6",
|
|
49
48
|
"@types/express": "^5.0.0",
|
|
50
|
-
"@types/findup-sync": "^4.0.5",
|
|
51
49
|
"@types/fs-extra": "^11.0.4",
|
|
52
50
|
"@types/js-yaml": "^4.0.9",
|
|
53
51
|
"@types/node": "^24.1.0",
|