| 22 | | { kind: "none" }; |
| 23 | |
| 24 | interface ResolveOptions { |
| 25 | /** Value of the `claudeUsage.cliPath` setting (empty string if unset). */ |
| 26 | configuredCliPath: string; |
| 27 | /** Path to the bundled `python/cli.py` shipped inside the .vsix. |
| 28 | * Always present in a packaged extension; absent only in tests. This is |
| 29 | * the default-and-most-reliable mode for marketplace users — they only |
| 30 | * need Python on PATH, no separate claude-usage install. */ |
| 31 | bundledCliPath?: string; |
| 32 | /** Absolute path to this extension's directory. Used to walk up to the repo root for the dev case. */ |
| 33 | extensionDir?: string; |
| 34 | /** VS Code workspace folder paths. Used as a discovery hint: if the user has |
| 35 | * the claude-usage repo open as their workspace, we'll find cli.py there. */ |
| 36 | workspaceFolders?: ReadonlyArray<string>; |
| 37 | /** Override env for tests. */ |
| 38 | env?: NodeJS.ProcessEnv; |
| 39 | } |
| 40 | |
| 41 | function claudeUsageCandidateNames(): string[] { |
| 42 | return IS_WIN ? ["claude-usage.exe", "claude-usage.cmd", "claude-usage"] : ["claude-usage"]; |
nothing calls this directly
no outgoing calls
no test coverage detected