document-cli 5.8.3 → 5.10.0

package/README.md

@@ -72,6 +72,8 @@ npm i -g doculi
 
 Both names install the exact same package and the exact same binary — `package.json`'s `bin` field declares both `document-cli` and `doculi` pointing at the one built entry point unconditionally, so there is no "real" name and an alias; pick whichever you find easier to type. Unlike a sibling's second _npm package name_ (`documents.js`'s own `js.documents` — see that package's README, and note the older per-repo pipeline's GitHub Packages republish this pattern used to mirror is no longer running, per [ExaDev/documents.js#732](https://github.com/ExaDev/documents.js/issues/732)), this is one package with two `bin` entries: a second name for the same build, not a second build, and unaffected by that gap.
 
+Every release also attaches a Node [single-executable application](https://nodejs.org/api/single-executable-applications.html) build for Linux, Windows, and macOS (both Apple Silicon and Intel) to that release's own GitHub Release assets — a standalone binary with the entire package and its dependencies embedded, needing no Node.js install or `npm i` at all. It covers every subcommand except the TUI, which needs a real terminal session rather than a spawned subprocess and stays npm-only; running `tui` against the binary prints a message pointing back at the npm-installed package instead of attempting to launch it. Download the asset matching your platform from the package's tag on the [Releases page](https://github.com/ExaDev/documents.js/releases) and run it directly (`chmod +x` on Linux/macOS first).
+
 ## Usage
 
 Every conversion and extraction command reads one input and writes one output. Pass `-` for either to use stdin/stdout instead of a file — useful for piping through other tools without a temp file:

package/dist/cli.js

@@ -1199,7 +1199,7 @@ function registerSetMetadataCommand(program) {
 }
 //#endregion
 //#region package.json
-var version = "5.8.3";
+var version = "5.10.0";
 //#endregion
 //#region src/program.ts
 function createProgram() {
@@ -1224,7 +1224,7 @@ function createProgram() {
 	return program;
 }
 //#endregion
-//#region src/cli.ts
+//#region src/cli-main.ts
 async function launchTui(startPath, signal) {
 	try {
 		const { runTui } = await import("./tui-CGo4rAhe.js");
@@ -1241,6 +1241,9 @@ async function launchTui(startPath, signal) {
 function findStartPath(args) {
 	return args.find((arg) => !arg.startsWith("-"));
 }
+/**
+* The real, full-featured CLI entry logic -- `src/cli.ts` (the published npm `bin`, run under a real Node.js install) awaits this at its own top level. The SEA build (`src/sea-entry.ts`) does NOT use this function; it uses `src/cli-main-sea.ts`'s own TUI-free equivalent instead, so that Ink's module graph is never reachable from the SEA bundle's own entry at all -- see this file's own top comment.
+*/
 async function main() {
 	const { signal } = createRuntimeSignal({});
 	const args = process.argv.slice(2);
@@ -1269,6 +1272,8 @@ async function main() {
 		if (!(error instanceof CommanderError)) throw error;
 	}
 }
+//#endregion
+//#region src/cli.ts
 await main();
 //#endregion
 export {};

package/dist/index.cjs

@@ -1549,7 +1549,7 @@ function registerSetMetadataCommand(program) {
 }
 //#endregion
 //#region package.json
-var version = "5.8.3";
+var version = "5.10.0";
 //#endregion
 //#region src/program.ts
 function createProgram() {

package/dist/index.js

@@ -1548,7 +1548,7 @@ function registerSetMetadataCommand(program) {
 }
 //#endregion
 //#region package.json
-var version = "5.8.3";
+var version = "5.10.0";
 //#endregion
 //#region src/program.ts
 function createProgram() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "document-cli",
-  "version": "5.8.3",
+  "version": "5.10.0",
   "description": "CLI and interactive Ink TUI for documents.js: every docx/pptx/odt/odp/ods/odg/odf/pdf/odm/odb/xlsx/csv/svg/markdown/rtf conversion, bridge, and editor as a scriptable command or a terminal app.",
   "type": "module",
   "repository": {