@gjsify/cli 0.44.0 → 0.46.0

package/lib/utils/ship/pe-launcher.d.ts

@@ -0,0 +1,29 @@
+/**
+ * `IMAGE_SUBSYSTEM_WINDOWS_GUI` — the one field this whole file exists to set.
+ *
+ * The counterpart is 3, `_CUI`, which is what `node.exe` and `cmd.exe` are and
+ * what makes Windows allocate a console when there is none to inherit.
+ */
+export declare const PE_SUBSYSTEM_GUI = 2;
+/** Where `Subsystem` lands in the emitted image: `e_lfanew` + 4 + 20 + 68. */
+export declare const PE_SUBSYSTEM_OFFSET: number;
+export interface GuiLauncherInput {
+    /**
+     * The file the stub writes the child's output to under `%TEMP%`, when there
+     * is no console to inherit.
+     *
+     * A LEAF and not a path: `%TEMP%` is the one directory a program can write to
+     * on every Windows install, and the program directory is not — `C:\Program
+     * Files\<App>` is read-only for the user who runs the app.
+     */
+    logLeaf: string;
+}
+/**
+ * The GUI-subsystem launcher, as a complete PE32+ image.
+ *
+ * Deterministic: the same input always produces the same bytes, with no
+ * timestamp, no checksum and no build-host string anywhere in the file — which
+ * is what lets `tests/e2e/ship-windows` compare two runs and what keeps the
+ * artifact reproducible for anyone who repacks a stage (ADR 0024 § A2).
+ */
+export declare function buildGuiLauncher(input: GuiLauncherInput): Uint8Array;