@silkweaver/build 1.0.0

package/README.md

@@ -0,0 +1,20 @@
+# @silkweaver/build
+
+The Silkweaver toolchain — turns a project folder into a runnable game. It's the engine room behind
+both the [`silkweaver` CLI](https://www.npmjs.com/package/@silkweaver/cli) and the IDE; most people
+will reach for one of those rather than this directly.
+
+It takes a project folder and produces a single self-contained `game.js` (the engine is inlined via
+esbuild), and can package that into a portable HTML5 build or a desktop executable.
+
+```ts
+import { build_preview, export_html5, export_executable } from '@silkweaver/build'
+
+await export_html5('./my-game', './dist')          // portable HTML5 folder
+await export_executable('./my-game', './dist', 'win32', 'x64')   // desktop build
+```
+
+It also exposes `object_format` — the parse/patch layer the IDE's object editor uses to edit
+class-per-object files surgically (preserving your hand-written code).
+
+Pure Node. Part of [Silkweaver](https://github.com/NicoNicoCip/Silkweaver). License: GPL-3.0.

package/dist/build.d.ts

@@ -0,0 +1,42 @@
+/**
+ * Game build / export logic for the Silkweaver desktop app.
+ *
+ * Pure Node code (fs/path/esbuild only — no electron imports) so it can be
+ * unit-tested and reused outside the IPC layer. main.ts wires these functions
+ * to the renderer over IPC.
+ *
+ * The engine, user scripts, and object code are all bundled into game.js by
+ * esbuild, so the ONLY difference between a preview build and an export build
+ * is how runtime asset URLs (sprite/background images) are resolved:
+ *   - 'preview': absolute file:// URLs into the live project folder (runs in the IDE)
+ *   - 'export':  relative 'assets/...' URLs (assets are copied next to game.js)
+ */
+import type { project_file as project_data } from '@silkweaver/project';
+export type { project_data };
+/** Reads and parses a project's project.json. */
+export declare function read_project(project_folder: string): Promise<project_data>;
+/**
+ * Builds the game to a single bundled game.js at out_path, for the in-IDE preview.
+ * @param out_path - Where to write game.js (the caller decides — e.g. exports/game.js)
+ */
+export declare function build_preview(project_folder: string, out_path: string): Promise<void>;
+/**
+ * Exports a portable, self-contained HTML5 build into out_dir:
+ *   out_dir/game.js     — minified, fully self-contained game (engine inlined)
+ *   out_dir/index.html  — standalone player page
+ *   out_dir/assets/...  — copied sprite/background assets (referenced relatively)
+ * @returns The export directory path.
+ */
+export declare function export_html5(project_folder: string, out_dir: string): Promise<string>;
+/**
+ * Exports a standalone desktop executable for the game.
+ *
+ * Stages a minimal Electron "player" app (a fixed main process that serves the
+ * exported game over a privileged `game://` protocol), then runs
+ * @electron/packager to produce a platform binary in out_dir.
+ *
+ * @param platform - 'win32' | 'darwin' | 'linux' (default 'win32')
+ * @param arch     - 'x64' | 'arm64' (default 'x64')
+ * @returns Absolute path to the packaged application folder.
+ */
+export declare function export_executable(project_folder: string, out_dir: string, platform?: string, arch?: string): Promise<string>;