@impetik/xeer-mcp 0.2.32 → 0.2.33
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 +2 -2
- package/vendor/spec/types.d.ts +7 -0
- package/vendor/spec/types.js +7 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@impetik/xeer-mcp",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.33",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Model Context Protocol server for Xeer project context, diagnostics, scaffold, check, test, dev, build, and preview deployment.",
|
|
6
6
|
"license": "MIT",
|
|
@@ -47,7 +47,7 @@
|
|
|
47
47
|
"dependencies": {
|
|
48
48
|
"@modelcontextprotocol/sdk": "^1.29.0",
|
|
49
49
|
"zod": "^4.0.10",
|
|
50
|
-
"@impetik/xeer": "0.2.
|
|
50
|
+
"@impetik/xeer": "0.2.33"
|
|
51
51
|
},
|
|
52
52
|
"devDependencies": {
|
|
53
53
|
"@types/node": "^24.1.0"
|
package/vendor/spec/types.d.ts
CHANGED
|
@@ -30,6 +30,13 @@ export declare const MAX_ASSET_BYTES: number;
|
|
|
30
30
|
* `Math.ceil(bytes / 3) * 4` against it.
|
|
31
31
|
*/
|
|
32
32
|
export declare const MAX_DEPLOYMENT_BASE64_BYTES: number;
|
|
33
|
+
/**
|
|
34
|
+
* The most the Worker modules of one deployment may inflate to when `xeer.deploy.v1` sends them gzipped.
|
|
35
|
+
* Below the 31.5 MiB of module bytes a 42 MiB plain payload could already decode to, so the control
|
|
36
|
+
* plane's peak during an upload (the parsed request plus the inflated modules) stays under what an
|
|
37
|
+
* uncompressed deployment could reach. A real EmDash site's modules are about 16 MiB.
|
|
38
|
+
*/
|
|
39
|
+
export declare const MAX_DEPLOYMENT_MODULE_BYTES: number;
|
|
33
40
|
export type DiagnosticSeverity = 'error' | 'warning' | 'info';
|
|
34
41
|
export interface SourceSpan {
|
|
35
42
|
line: number;
|
package/vendor/spec/types.js
CHANGED
|
@@ -28,6 +28,13 @@ export const MAX_ASSET_BYTES = 25 * 1024 * 1024;
|
|
|
28
28
|
* `Math.ceil(bytes / 3) * 4` against it.
|
|
29
29
|
*/
|
|
30
30
|
export const MAX_DEPLOYMENT_BASE64_BYTES = 42 * 1024 * 1024;
|
|
31
|
+
/**
|
|
32
|
+
* The most the Worker modules of one deployment may inflate to when `xeer.deploy.v1` sends them gzipped.
|
|
33
|
+
* Below the 31.5 MiB of module bytes a 42 MiB plain payload could already decode to, so the control
|
|
34
|
+
* plane's peak during an upload (the parsed request plus the inflated modules) stays under what an
|
|
35
|
+
* uncompressed deployment could reach. A real EmDash site's modules are about 16 MiB.
|
|
36
|
+
*/
|
|
37
|
+
export const MAX_DEPLOYMENT_MODULE_BYTES = 24 * 1024 * 1024;
|
|
31
38
|
/**
|
|
32
39
|
* Whether a set of diagnostics refuses the command that produced it.
|
|
33
40
|
*
|