@adhdev/daemon-core 0.9.82-rc.300 → 0.9.82-rc.302
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/dist/cli-adapters/resolve-executable.d.ts +14 -0
- package/dist/index.js +506 -462
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +511 -467
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -2
- package/src/cli-adapters/pty-transport.ts +2 -1
- package/src/cli-adapters/resolve-executable.ts +45 -0
- package/src/cli-adapters/session-host-transport.ts +2 -1
- package/src/commands/upgrade-helper.ts +29 -0
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Resolve a launch command to an absolute executable path on Windows.
|
|
3
|
+
*
|
|
4
|
+
* node-pty's ConPTY backend resolves a bare/relative command against the
|
|
5
|
+
* *calling process's* `Path` env var and — critically — does NOT apply PATHEXT.
|
|
6
|
+
* So a provider command like `claude` never matches `claude.exe` and the native
|
|
7
|
+
* layer throws `File not found:` (empty), which crashes the daemon. We resolve
|
|
8
|
+
* it to an absolute `.exe` here (in the daemon process, which has the full PATH)
|
|
9
|
+
* before the command ever reaches node-pty.
|
|
10
|
+
*
|
|
11
|
+
* No-op on non-Windows and when the command is already an existing absolute path
|
|
12
|
+
* or cannot be resolved (caller keeps the original behaviour).
|
|
13
|
+
*/
|
|
14
|
+
export declare function resolveWin32Executable(command: string): string;
|