pi-cache-optimizer 2.8.0 → 2.8.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
@@ -55,7 +55,7 @@ Run `/reload` in Pi after install/update/remove so extension hooks refresh.
55
55
 
56
56
  On Pi 0.79.7 and newer, `pi update` updates Pi itself only. To update installed Pi packages such as this extension, run `pi update --extensions` (packages only) or `pi update --all` (Pi + packages).
57
57
 
58
- This extension is validated against Pi 0.83.0 and remains designed for Pi 0.82+. It uses the existing extension hooks, `getAgentDir()`, and prompt options shared by those versions; it does not depend on Pi 0.83-only APIs such as `ctx.scopedModels` or the bundled TypeBox 1.3 aliases.
58
+ This extension is validated against Pi 0.84.1 and remains designed for Pi 0.82+. It uses the existing extension hooks, `getAgentDir()`, and prompt options shared by those versions; it does not depend on Pi 0.83+ APIs such as `ctx.scopedModels` or the bundled TypeBox 1.3 aliases.
59
59
 
60
60
  ## Commands
61
61
 
@@ -71,6 +71,8 @@ This extension is validated against Pi 0.83.0 and remains designed for Pi 0.82+.
71
71
  | `/cache-optimizer config footer-mode total\|session\|process` | Persist the footer stats mode. Persistent command configuration overrides the environment variable. |
72
72
  | `/cache-optimizer fix` | Auto-repairs safe compat issues for the active model (adaptive thinking, DeepSeek reasoning, OpenAI proxy session affinity). Shows preview + risk warning, requires confirmation. **Only modifies `models.json` after explicit user approval.** |
73
73
 
74
+ `/cache-optimizer` uses Pi's native Tab completion. Type `/cache-optimizer <Tab>` for the supported subcommands, `/cache-optimizer c<Tab>` for `config`, `/cache-optimizer config <Tab>` for `footer-mode`, and `/cache-optimizer config footer-mode <Tab>` for `total`, `session`, or `process`. Suggestions are prefix-filtered and invalid prefixes are left to Pi's normal fallback behavior.
75
+
74
76
  The interactive `/cache-optimizer` menu includes `Footer mode`, where you can choose `total`, `session`, or `process`. `enable` / `disable` are current-process switches. For a persistent opt-out, use environment variables below.
75
77
 
76
78
  ## Persistent opt-out
@@ -107,7 +109,7 @@ The explicit setting is stored in `pi-cache-optimizer-config.json` under Pi's ag
107
109
 
108
110
  Third-party `openai-completions` proxies (LiteLLM / OneAPI / NewAPI / OpenRouter-like channels) often route one session across multiple upstream backends. That splits provider-side prompt caches.
109
111
 
110
- Pi 0.81+ also has a built-in `llama.cpp` provider using an OpenAI-shaped transport. Pi 0.82+ core generates a session `prompt_cache_key` for it when cache retention is enabled, so this extension preserves that key and may add the same conservative fallback when missing. The built-in provider's explicit compat fingerprint is excluded from generic proxy routing/session-affinity advice, but a custom or overridden provider that merely reuses the id `llama.cpp` is treated like any other OpenAI-compatible channel. `prompt_cache_retention` remains subject to the normal safety rule: keep it only for official OpenAI or an explicit effective `supportsLongCacheRetention: true` opt-in in `models.json`; otherwise strip it before sending. Effective values follow Pi's precedence: `modelOverrides[modelId].compat` first, then the matching `models[].compat`, then provider-level `compat`. An explicit `false` at a higher layer overrides `true` below it.
112
+ Pi 0.84.1 also fixes built-in Fireworks compatibility for models that reject `prompt_cache_retention`; keep the extension's diagnostics focused on the effective model compat exposed by Pi rather than adding a provider-name special case. Pi 0.81+ also has a built-in `llama.cpp` provider using an OpenAI-shaped transport. Pi 0.82+ core generates a session `prompt_cache_key` for it when cache retention is enabled, so this extension preserves that key and may add the same conservative fallback when missing. The built-in provider's explicit compat fingerprint is excluded from generic proxy routing/session-affinity advice, but a custom or overridden provider that merely reuses the id `llama.cpp` is treated like any other OpenAI-compatible channel. `prompt_cache_retention` remains subject to the normal safety rule: keep it only for official OpenAI or an explicit effective `supportsLongCacheRetention: true` opt-in in `models.json`; otherwise strip it before sending. Effective values follow Pi's precedence: `modelOverrides[modelId].compat` first, then the matching `models[].compat`, then provider-level `compat`. An explicit `false` at a higher layer overrides `true` below it.
111
113
 
112
114
  For real proxies, start with session affinity:
113
115
 
@@ -148,7 +150,7 @@ Some proxies rewrite or insert hidden 5-minute breakpoints after Pi's request ho
148
150
 
149
151
  ## Adaptive thinking models
150
152
 
151
- Claude models from opus-4.6 / sonnet-4.6 (including Opus 5 and Sonnet 5) / fable-5 onwards require `forceAdaptiveThinking: true` in compat. Kimi Coding K3 (`k3`) and `kimi-for-coding` also use adaptive thinking and need `allowEmptySignature: true` so replayed empty-signature thinking blocks remain valid. Without the required compat, Pi may send a legacy thinking payload or replay thinking incorrectly. Pi 0.83.0's native Opus 5 catalog is covered by the same adaptive-thinking detection; custom `anthropic-messages` channels still need the compat flag when Pi does not provide it.
153
+ Claude models from opus-4.6 / sonnet-4.6 (including Opus 5 and Sonnet 5) / fable-5 onwards require `forceAdaptiveThinking: true` in compat. Kimi Coding K3 (`k3`) and `kimi-for-coding` also use adaptive thinking and need `allowEmptySignature: true` so replayed empty-signature thinking blocks remain valid. Without the required compat, Pi may send a legacy thinking payload or replay thinking incorrectly. Pi 0.83+ native Opus 5 catalogs are covered by the same adaptive-thinking detection; custom `anthropic-messages` channels still need the compat flag when Pi does not provide it.
152
154
 
153
155
  Pi's built-in catalog already sets this flag for official models. Custom channels in `models.json` that override these models must include the flag:
154
156
 
@@ -281,10 +283,10 @@ Pi 0.79+ also includes a built-in footer `CH` marker for the latest prompt cache
281
283
  Example footer:
282
284
 
283
285
  ```text
284
- OpenAI cache 3/10 · 0.002M/0.005M tok (40%) ⚠️ compat
286
+ · OpenAI cache 3/10·0.002M/0.005M 40.0% ⚠️ compat
285
287
  ```
286
288
 
287
- Format: `<label> <hit requests>/<total requests> · <cached input tokens>/<total input tokens> tok (<token hit rate>)`. Some adapters may also append `· write <tokens> tok`, and runtime diagnostics may append `⚠️ compat` or `⚠️ integrity`.
289
+ The leading `· ` is owned by this extension and separates its status from statuses published by other extensions in the same footer. It is present for normal, disabled, router-restored, and warning-suffixed statuses. The compact footer format is `<label> <hit requests>/<total requests>·<cached input tokens>/<total input tokens> <token hit rate>`; token hit rate keeps one decimal place and the footer omits the redundant `tok` suffix. `/cache-optimizer stats` output is unchanged. Some adapters may also append `·write <tokens>`, and runtime diagnostics may append `⚠️ compat` or `⚠️ integrity`.
288
290
 
289
291
  Supported footer labels include: DS, Claude, OpenAI, Gemini, Kimi, Qwen, GLM, MiniMax, Mimo, Hunyuan, Mistral, Grok, Llama, Nemotron, Cohere, Yi, Doubao, ERNIE, Baichuan, StepFun, Spark, InternLM, Gemma, Phi, Jamba, Solar, Sonar, Nova, Reka, Falcon, DBRX, MPT, StableLM, Aquila, EXAONE, HyperCLOVA, Luminous, Hermes, Granite, Arctic, Pangu, SenseNova, Zhinao, MiniCPM, XVERSE, Orion, OpenChat, Vicuna, Wizard, Zephyr, Dolphin, OpenOrca, Starling, BLOOM, RWKV, and Aya.
290
292
 
package/README.zh-CN.md CHANGED
@@ -55,7 +55,7 @@ pi remove npm:pi-deepseek-cache-optimizer && pi install npm:pi-cache-optimizer
55
55
 
56
56
  Pi 0.79.7 及之后,`pi update` 默认只更新 Pi 本体。若要更新已安装的 Pi package(包括本扩展),请运行 `pi update --extensions`(只更新 packages)或 `pi update --all`(Pi 与 packages 一起更新)。
57
57
 
58
- 本扩展已使用 Pi 0.83.0 验证,并继续面向 Pi 0.82+ 设计。它使用这些版本共有的 extension hooks、`getAgentDir()` 和 prompt options,不依赖 Pi 0.83 专有 API(例如 `ctx.scopedModels` 或 bundled TypeBox 1.3 aliases)。
58
+ 本扩展已使用 Pi 0.84.1 验证,并继续面向 Pi 0.82+ 设计。它使用这些版本共有的 extension hooks、`getAgentDir()` 和 prompt options,不依赖 Pi 0.83+ 专有 API(例如 `ctx.scopedModels` 或 bundled TypeBox 1.3 aliases)。
59
59
 
60
60
  ## 命令
61
61
 
@@ -71,6 +71,8 @@ Pi 0.79.7 及之后,`pi update` 默认只更新 Pi 本体。若要更新已安
71
71
  | `/cache-optimizer config footer-mode total\|session\|process` | 持久设置 footer 统计模式;持久命令配置优先于环境变量。 |
72
72
  | `/cache-optimizer fix` | 为当前模型自动修复安全的 compat 问题(adaptive thinking、DeepSeek reasoning、OpenAI proxy session affinity)。展示预览 + 风险提示,需要用户确认。**仅在用户明确批准后才修改 `models.json`。** |
73
73
 
74
+ `/cache-optimizer` 使用 Pi 原生 Tab 补全:输入 `/cache-optimizer <Tab>` 查看支持的子命令,输入 `/cache-optimizer c<Tab>` 补全 `config`,输入 `/cache-optimizer config <Tab>` 补全 `footer-mode`,输入 `/cache-optimizer config footer-mode <Tab>` 补全 `total`、`session` 或 `process`。建议会按当前前缀过滤;无效前缀返回空结果,由 Pi 正常回退处理。
75
+
74
76
  交互式 `/cache-optimizer` 菜单包含 `Footer mode`,可以选择 `total`、`session` 或 `process`。`enable` / `disable` 是当前进程内开关。若要持久关闭某些能力,请使用下面的环境变量。
75
77
 
76
78
  ## 持久 Opt-out
@@ -106,7 +108,7 @@ Pi 0.79.7 及之后,`pi update` 默认只更新 Pi 本体。若要更新已安
106
108
 
107
109
  LiteLLM / OneAPI / NewAPI / 类 OpenRouter 渠道等第三方 `openai-completions` 代理,常会把同一个 session 分散到多个上游后端,导致 provider 侧 prompt cache 被拆散。
108
110
 
109
- Pi 0.81+ 也内置了使用 OpenAI-shaped transport 的 `llama.cpp` provider。Pi 0.82+ core 在启用 cache retention 时会为它生成 session `prompt_cache_key`,因此本扩展会保留该 key,并在缺失时使用同样的保守 fallback。只有符合 Pi 内置 provider 明确 compat 指纹的模型会跳过通用 proxy 路由 / session-affinity 建议;仅复用 `llama.cpp` id 的自定义或覆盖 provider 仍按普通 OpenAI-compatible 渠道处理。`prompt_cache_retention` 继续遵循统一安全规则:仅官方 OpenAI 或 `models.json` 中有效配置为 `supportsLongCacheRetention: true` 时保留,否则发送前移除。有效值遵循 Pi 的优先级:先看 `modelOverrides[modelId].compat`,再看匹配的 `models[].compat`,最后看 provider 级 `compat`;高层显式 `false` 会覆盖低层的 `true`。
111
+ Pi 0.84.1 还修复了内置 Fireworks 渠道对拒绝 `prompt_cache_retention` 的模型兼容性;本扩展继续依据 Pi 暴露的有效 model compat 做诊断,不按 provider 名称增加特殊分支。Pi 0.81+ 也内置了使用 OpenAI-shaped transport 的 `llama.cpp` provider。Pi 0.82+ core 在启用 cache retention 时会为它生成 session `prompt_cache_key`,因此本扩展会保留该 key,并在缺失时使用同样的保守 fallback。只有符合 Pi 内置 provider 明确 compat 指纹的模型会跳过通用 proxy 路由 / session-affinity 建议;仅复用 `llama.cpp` id 的自定义或覆盖 provider 仍按普通 OpenAI-compatible 渠道处理。`prompt_cache_retention` 继续遵循统一安全规则:仅官方 OpenAI 或 `models.json` 中有效配置为 `supportsLongCacheRetention: true` 时保留,否则发送前移除。有效值遵循 Pi 的优先级:先看 `modelOverrides[modelId].compat`,再看匹配的 `models[].compat`,最后看 provider 级 `compat`;高层显式 `false` 会覆盖低层的 `true`。
110
112
 
111
113
  对真正的代理,建议先启用 session affinity:
112
114
 
@@ -147,7 +149,7 @@ Anthropic 按 `tools → system → messages` 顺序处理 cache breakpoint,
147
149
 
148
150
  ## Adaptive thinking 模型
149
151
 
150
- Claude 从 opus-4.6 / sonnet-4.6(含 Opus 5、Sonnet 5)/ fable-5 开始需要在 compat 中设置 `forceAdaptiveThinking: true`。Kimi Coding K3(`k3`)和 `kimi-for-coding` 也使用 adaptive thinking,并需要 `allowEmptySignature: true`,以正确重放空 signature 的 thinking block。缺少这些 compat 时,Pi 可能发送旧版 thinking payload 或错误重放 thinking。Pi 0.83.0 的原生 Opus 5 catalog 已覆盖在同一 adaptive-thinking 检测中;如果自定义 `anthropic-messages` 渠道没有继承该 compat,仍需手动设置。
152
+ Claude 从 opus-4.6 / sonnet-4.6(含 Opus 5、Sonnet 5)/ fable-5 开始需要在 compat 中设置 `forceAdaptiveThinking: true`。Kimi Coding K3(`k3`)和 `kimi-for-coding` 也使用 adaptive thinking,并需要 `allowEmptySignature: true`,以正确重放空 signature 的 thinking block。缺少这些 compat 时,Pi 可能发送旧版 thinking payload 或错误重放 thinking。Pi 0.83+ 的原生 Opus 5 catalog 已覆盖在同一 adaptive-thinking 检测中;如果自定义 `anthropic-messages` 渠道没有继承该 compat,仍需手动设置。
151
153
 
152
154
  Pi 内置 catalog 已为官方模型设置此 flag。`models.json` 中覆盖这些模型的自定义渠道必须包含该 flag:
153
155
 
@@ -280,10 +282,10 @@ Pi 0.79+ 已内置 footer `CH` 标记,用于显示最近一次 prompt cache hi
280
282
  示例 footer:
281
283
 
282
284
  ```text
283
- OpenAI cache 3/10 · 0.002M/0.005M tok (40%) ⚠️ compat
285
+ · OpenAI cache 3/10·0.002M/0.005M 40.0% ⚠️ compat
284
286
  ```
285
287
 
286
- 格式:`<label> <命中请求数>/<总请求数> · <cached input tokens>/<total input tokens> tok (<token 命中率>)`。部分 adapter 还可能追加 `· write <tokens> tok`,运行时诊断可能追加 `⚠️ compat` 或 `⚠️ integrity`。
288
+ 开头的 `· ` 由本扩展负责,用于把本扩展状态与同一 footer 中其他扩展发布的状态隔开。普通、disabled、router 恢复以及带 warning 的状态都会保留此前缀。紧凑 footer 格式为 `<label> <命中请求数>/<总请求数>·<cached input tokens>/<total input tokens> <token 命中率>`;token 命中率保留一位小数,并去掉多余的 `tok` 后缀。`/cache-optimizer stats` 的输出不变。部分 adapter 还可能追加 `·write <tokens>`,运行时诊断可能追加 `⚠️ compat` 或 `⚠️ integrity`。
287
289
 
288
290
  支持的 footer label 包括:DS、Claude、OpenAI、Gemini、Kimi、Qwen、GLM、MiniMax、Mimo、Hunyuan、Mistral、Grok、Llama、Nemotron、Cohere、Yi、Doubao、ERNIE、Baichuan、StepFun、Spark、InternLM、Gemma、Phi、Jamba、Solar、Sonar、Nova、Reka、Falcon、DBRX、MPT、StableLM、Aquila、EXAONE、HyperCLOVA、Luminous、Hermes、Granite、Arctic、Pangu、SenseNova、Zhinao、MiniCPM、XVERSE、Orion、OpenChat、Vicuna、Wizard、Zephyr、Dolphin、OpenOrca、Starling、BLOOM、RWKV、Aya。
289
291
 
package/index.ts CHANGED
@@ -1146,6 +1146,82 @@ function parseFooterStatsMode(value: unknown): FooterStatsMode | undefined {
1146
1146
  return normalized === "session" || normalized === "total" || normalized === "process" ? normalized : undefined;
1147
1147
  }
1148
1148
 
1149
+ type CommandCompletionItem = {
1150
+ value: string;
1151
+ label: string;
1152
+ description?: string;
1153
+ };
1154
+
1155
+ const CACHE_OPTIMIZER_COMMANDS = [
1156
+ "enable",
1157
+ "disable",
1158
+ "doctor",
1159
+ "stats",
1160
+ "config",
1161
+ "compat",
1162
+ "reset",
1163
+ "fix",
1164
+ ] as const;
1165
+ const CACHE_OPTIMIZER_CONFIG_ARGUMENTS = ["footer-mode"] as const;
1166
+ const CACHE_OPTIMIZER_FOOTER_MODES = ["total", "session", "process"] as const;
1167
+
1168
+ function filterCommandCompletionItems(
1169
+ values: readonly string[],
1170
+ prefix: string,
1171
+ argumentPath = "",
1172
+ ): CommandCompletionItem[] | null {
1173
+ const normalizedPrefix = prefix.trim().toLowerCase();
1174
+ const matches = values
1175
+ .filter((value) => value.startsWith(normalizedPrefix))
1176
+ .map((value) => ({
1177
+ // Pi replaces the complete argumentPrefix when applying a command
1178
+ // completion, so nested suggestions must include their full path.
1179
+ value: argumentPath ? `${argumentPath} ${value}` : value,
1180
+ label: value,
1181
+ }));
1182
+ return matches.length > 0 ? matches : null;
1183
+ }
1184
+
1185
+ function getCacheOptimizerArgumentCompletions(argumentPrefix: string): CommandCompletionItem[] | null {
1186
+ if (typeof argumentPrefix !== "string") return null;
1187
+ const trimmed = argumentPrefix.trim();
1188
+ const parts = trimmed ? trimmed.split(/\s+/) : [];
1189
+
1190
+ if (parts.length === 0) {
1191
+ return filterCommandCompletionItems(CACHE_OPTIMIZER_COMMANDS, "");
1192
+ }
1193
+
1194
+ if (parts.length === 1) {
1195
+ const subcommandPrefix = parts[0].toLowerCase();
1196
+ // `config` is the primary `c` completion; `compat` remains available
1197
+ // through its more specific `co` prefix. Surrounding whitespace is
1198
+ // ignored so ` c ` behaves the same as `c`.
1199
+ if (subcommandPrefix === "c") {
1200
+ return [{ value: "config", label: "config" }];
1201
+ }
1202
+ if (subcommandPrefix === "config") {
1203
+ return filterCommandCompletionItems(CACHE_OPTIMIZER_CONFIG_ARGUMENTS, "", "config");
1204
+ }
1205
+ return filterCommandCompletionItems(CACHE_OPTIMIZER_COMMANDS, parts[0]);
1206
+ }
1207
+
1208
+ if (parts[0].toLowerCase() !== "config") return null;
1209
+
1210
+ if (parts.length === 2) {
1211
+ const nestedPrefix = parts[1].toLowerCase();
1212
+ if (nestedPrefix === "footer-mode") {
1213
+ return filterCommandCompletionItems(CACHE_OPTIMIZER_FOOTER_MODES, "", "config footer-mode");
1214
+ }
1215
+ return filterCommandCompletionItems(CACHE_OPTIMIZER_CONFIG_ARGUMENTS, parts[1], "config");
1216
+ }
1217
+
1218
+ if (parts.length === 3 && parts[1].toLowerCase() === "footer-mode") {
1219
+ return filterCommandCompletionItems(CACHE_OPTIMIZER_FOOTER_MODES, parts[2], "config footer-mode");
1220
+ }
1221
+
1222
+ return null;
1223
+ }
1224
+
1149
1225
  function parsePersistedCacheOptimizerConfig(value: unknown): PersistedCacheOptimizerConfigV1 | undefined {
1150
1226
  const record = asRecord(value);
1151
1227
  if (!record || record.version !== 1) return undefined;
@@ -3657,13 +3733,18 @@ function formatTokenCount(value: number): string {
3657
3733
 
3658
3734
  function formatCacheStats(adapter: CacheProviderAdapter, stats: CacheStats): string {
3659
3735
  const percent = stats.totalInputTokens > 0
3660
- ? ` (${Math.round((stats.cachedInputTokens / stats.totalInputTokens) * 100)}%)`
3661
- : "";
3736
+ ? (stats.cachedInputTokens / stats.totalInputTokens) * 100
3737
+ : 0;
3662
3738
  const writeText = adapter.showCacheWrite && stats.cacheWriteInputTokens > 0
3663
- ? ` · write ${formatTokenCount(stats.cacheWriteInputTokens)} tok`
3739
+ ? `·write ${formatTokenCount(stats.cacheWriteInputTokens)}`
3664
3740
  : "";
3665
3741
 
3666
- return `${adapter.label} ${stats.hitRequests}/${stats.totalRequests} · ${formatTokenCount(stats.cachedInputTokens)}/${formatTokenCount(stats.totalInputTokens)} tok${percent}${writeText}`;
3742
+ return `${adapter.label} ${stats.hitRequests}/${stats.totalRequests}·${formatTokenCount(stats.cachedInputTokens)}/${formatTokenCount(stats.totalInputTokens)} ${percent.toFixed(1)}%${writeText}`;
3743
+ }
3744
+
3745
+ function prefixFooterStatus(statusText: string | undefined): string | undefined {
3746
+ if (!statusText || statusText.startsWith("· ")) return statusText;
3747
+ return `· ${statusText}`;
3667
3748
  }
3668
3749
 
3669
3750
  /**
@@ -6653,6 +6734,8 @@ export const __internals_for_tests = {
6653
6734
  // Cache stats helpers (module-level, usable from verify script)
6654
6735
  addUsageToCacheStats,
6655
6736
  formatCacheStats,
6737
+ prefixFooterStatus,
6738
+ getCacheOptimizerArgumentCompletions,
6656
6739
  emptyCacheStats,
6657
6740
  emptyAllCacheStats,
6658
6741
  parseCacheStats,
@@ -7240,6 +7323,7 @@ export default function (pi: ExtensionAPI) {
7240
7323
  }
7241
7324
  }
7242
7325
 
7326
+ statusText = prefixFooterStatus(statusText);
7243
7327
  if (statusText === lastStatusText) return;
7244
7328
 
7245
7329
  lastStatusText = statusText;
@@ -7647,6 +7731,7 @@ export default function (pi: ExtensionAPI) {
7647
7731
  // ────────────────────────────────────────────────────────────────
7648
7732
  pi.registerCommand("cache-optimizer", {
7649
7733
  description: "Configure and diagnose Pi cache behavior",
7734
+ getArgumentCompletions: getCacheOptimizerArgumentCompletions,
7650
7735
  handler: async (args: string, cmdCtx) => {
7651
7736
  syncSessionHash(cmdCtx);
7652
7737
  const selectedModel = cmdCtx.model;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-cache-optimizer",
3
- "version": "2.8.0",
3
+ "version": "2.8.2",
4
4
  "description": "Improve Pi prompt/KV cache hit rates with stable prompts, OpenAI-compatible cache keys, proxy compat warnings, and footer cache stats.",
5
5
  "keywords": [
6
6
  "pi-package",
@@ -35,6 +35,7 @@
35
35
  "check": "npm run typecheck && npm test && npm run check:diff && npm run check:pack"
36
36
  },
37
37
  "devDependencies": {
38
+ "@earendil-works/pi-coding-agent": "^0.84.1",
38
39
  "@types/node": "^22.0.0",
39
40
  "jiti": "^2.7.0",
40
41
  "typescript": "^5.8.3"