@rebasepro/cli 0.23.0 → 0.24.1-canary.g19596ef

package/dist/path-flags-BFgG9V6y.js

@@ -0,0 +1,91 @@
+import chalk from "chalk";
+import fs from "fs";
+import path from "path";
+//#region src/utils/path-flags.ts
+/**
+* Where a path typed on a `rebase` command line resolves: one rule, one sentence.
+*
+* The driver CLI runs with `cwd: backend/` — that is where it and its
+* dependencies resolve from — while people type commands from the project root
+* (or anywhere else in it). So every relative path on the line is resolved by
+* the CLI, from the directory the command was run in, before the driver is
+* handed a different one (`absolutizeLocalPathArgs` in `commands/db.ts`).
+* `generate-sdk` and `db backup --out` already worked that way; `--collections`
+* was resolved from `backend/` and was the odd one out.
+*
+* The sentence below is printed by every help page that takes `--collections`,
+* and by the refusal when the path is not there, so the rule is stated in one
+* set of words wherever a reader meets it.
+*/
+/** The rule, as every help page and error states it. */
+var COLLECTIONS_PATH_RULE = "relative paths are resolved from where you run the command";
+/** The `--collections` line of a help page. */
+var COLLECTIONS_FLAG_HELP = `Collections directory (default: config/collections); ${COLLECTIONS_PATH_RULE}`;
+/** The flags that carry a collections path, in every spelling the driver accepts. */
+var COLLECTIONS_FLAGS = ["--collections", "-c"];
+/** The `--collections` value on a line, as typed, or `null` when there is none. */
+function typedCollectionsPath(args) {
+	for (let i = 0; i < args.length; i++) {
+		const token = args[i];
+		const eq = token.indexOf("=");
+		if (eq > 0 && COLLECTIONS_FLAGS.includes(token.slice(0, eq))) return token.slice(eq + 1) || null;
+		if (COLLECTIONS_FLAGS.includes(token)) {
+			const value = args[i + 1];
+			return value && !value.startsWith("-") ? value : null;
+		}
+	}
+	return null;
+}
+/**
+* What a refusal over a missing `--collections` path spared, by what the command
+* would have done with it. Only a schema writer drops tables; a console or a
+* doctor run over nothing does something else wrong, and says so.
+*/
+var MISSING_COLLECTIONS_CONSEQUENCE = {
+	schema: [
+		"Nothing was generated and nothing was applied — a schema generated from a",
+		"directory that is not there is an empty one, and applying it would drop",
+		"every table it does not describe."
+	],
+	console: ["Nothing was started — a console over a directory that is not there would", "load none of this project's collections."],
+	doctor: ["Nothing was checked — a directory that is not there has no collections, so", "every collection check would pass over it."]
+};
+/**
+* The refusal for a `--collections` path that does not exist, or `null`.
+*
+* Checked by the CLI, in the reader's terms, before the driver is spawned: the
+* driver's own check runs in `backend/` and can only describe the path it was
+* handed. A generator pointed at a directory that is not there writes an empty
+* schema, and a push of an empty schema drops every table — so nothing runs.
+*
+* Scripts written for the old rule (`--collections ../config/collections`,
+* run from the root) land here, and the message says exactly what to change.
+*/
+function missingCollectionsPath(args, cwd, backendDir, use = "schema") {
+	const typed = typedCollectionsPath(args);
+	if (typed === null) return null;
+	const resolved = path.resolve(cwd, typed);
+	if (fs.existsSync(resolved)) return null;
+	const lines = [
+		chalk.red(`✗ Collections path not found: "${typed}"`),
+		chalk.gray(`    Resolved to: ${resolved}`),
+		chalk.gray(`    (${COLLECTIONS_PATH_RULE}: ${cwd})`)
+	];
+	const fromBackend = path.resolve(backendDir, typed);
+	if (!path.isAbsolute(typed) && fs.existsSync(fromBackend)) lines.push("", chalk.yellow(`  From backend/ it would be ${fromBackend} — the driver used to resolve paths from there.`), chalk.yellow(`  Leave the flag out (config/collections is the default), or write it from here: ${path.relative(cwd, fromBackend) || "."}`));
+	lines.push("", ...MISSING_COLLECTIONS_CONSEQUENCE[use].map((line) => chalk.gray(`  ${line}`)));
+	return lines;
+}
+/** Print {@link missingCollectionsPath}'s refusal and exit 1, or return. */
+function refuseMissingCollectionsPath(args, cwd, backendDir, use = "schema") {
+	const lines = missingCollectionsPath(args, cwd, backendDir, use);
+	if (!lines) return;
+	console.error("");
+	for (const line of lines) console.error(line);
+	console.error("");
+	process.exit(1);
+}
+//#endregion
+export { COLLECTIONS_PATH_RULE as n, refuseMissingCollectionsPath as r, COLLECTIONS_FLAG_HELP as t };
+
+//# sourceMappingURL=path-flags-BFgG9V6y.js.map

package/dist/path-flags-BFgG9V6y.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"path-flags-BFgG9V6y.js","names":[],"sources":["../src/utils/path-flags.ts"],"sourcesContent":["/**\n * Where a path typed on a `rebase` command line resolves: one rule, one sentence.\n *\n * The driver CLI runs with `cwd: backend/` — that is where it and its\n * dependencies resolve from — while people type commands from the project root\n * (or anywhere else in it). So every relative path on the line is resolved by\n * the CLI, from the directory the command was run in, before the driver is\n * handed a different one (`absolutizeLocalPathArgs` in `commands/db.ts`).\n * `generate-sdk` and `db backup --out` already worked that way; `--collections`\n * was resolved from `backend/` and was the odd one out.\n *\n * The sentence below is printed by every help page that takes `--collections`,\n * and by the refusal when the path is not there, so the rule is stated in one\n * set of words wherever a reader meets it.\n */\nimport fs from \"fs\";\nimport path from \"path\";\nimport chalk from \"chalk\";\n\n/** The rule, as every help page and error states it. */\nexport const COLLECTIONS_PATH_RULE = \"relative paths are resolved from where you run the command\";\n\n/** The `--collections` line of a help page. */\nexport const COLLECTIONS_FLAG_HELP = `Collections directory (default: config/collections); ${COLLECTIONS_PATH_RULE}`;\n\n/** The flags that carry a collections path, in every spelling the driver accepts. */\nconst COLLECTIONS_FLAGS = [\"--collections\", \"-c\"];\n\n/** The `--collections` value on a line, as typed, or `null` when there is none. */\nfunction typedCollectionsPath(args: readonly string[]): string | null {\n    for (let i = 0; i < args.length; i++) {\n        const token = args[i];\n        const eq = token.indexOf(\"=\");\n        if (eq > 0 && COLLECTIONS_FLAGS.includes(token.slice(0, eq))) return token.slice(eq + 1) || null;\n        if (COLLECTIONS_FLAGS.includes(token)) {\n            const value = args[i + 1];\n            return value && !value.startsWith(\"-\") ? value : null;\n        }\n    }\n    return null;\n}\n\n/**\n * What a refusal over a missing `--collections` path spared, by what the command\n * would have done with it. Only a schema writer drops tables; a console or a\n * doctor run over nothing does something else wrong, and says so.\n */\nconst MISSING_COLLECTIONS_CONSEQUENCE = {\n    schema: [\n        \"Nothing was generated and nothing was applied — a schema generated from a\",\n        \"directory that is not there is an empty one, and applying it would drop\",\n        \"every table it does not describe.\"\n    ],\n    console: [\n        \"Nothing was started — a console over a directory that is not there would\",\n        \"load none of this project's collections.\"\n    ],\n    doctor: [\n        \"Nothing was checked — a directory that is not there has no collections, so\",\n        \"every collection check would pass over it.\"\n    ]\n} as const;\n\n/** What a command does with its `--collections` path. */\nexport type CollectionsPathUse = keyof typeof MISSING_COLLECTIONS_CONSEQUENCE;\n\n/**\n * The refusal for a `--collections` path that does not exist, or `null`.\n *\n * Checked by the CLI, in the reader's terms, before the driver is spawned: the\n * driver's own check runs in `backend/` and can only describe the path it was\n * handed. A generator pointed at a directory that is not there writes an empty\n * schema, and a push of an empty schema drops every table — so nothing runs.\n *\n * Scripts written for the old rule (`--collections ../config/collections`,\n * run from the root) land here, and the message says exactly what to change.\n */\nexport function missingCollectionsPath(\n    args: readonly string[],\n    cwd: string,\n    backendDir: string,\n    use: CollectionsPathUse = \"schema\"\n): string[] | null {\n    const typed = typedCollectionsPath(args);\n    if (typed === null) return null;\n    const resolved = path.resolve(cwd, typed);\n    if (fs.existsSync(resolved)) return null;\n\n    const lines = [\n        chalk.red(`✗ Collections path not found: \"${typed}\"`),\n        chalk.gray(`    Resolved to: ${resolved}`),\n        chalk.gray(`    (${COLLECTIONS_PATH_RULE}: ${cwd})`)\n    ];\n    const fromBackend = path.resolve(backendDir, typed);\n    if (!path.isAbsolute(typed) && fs.existsSync(fromBackend)) {\n        lines.push(\n            \"\",\n            chalk.yellow(`  From backend/ it would be ${fromBackend} — the driver used to resolve paths from there.`),\n            chalk.yellow(`  Leave the flag out (config/collections is the default), or write it from here: ${path.relative(cwd, fromBackend) || \".\"}`)\n        );\n    }\n    lines.push(\"\", ...MISSING_COLLECTIONS_CONSEQUENCE[use].map(line => chalk.gray(`  ${line}`)));\n    return lines;\n}\n\n/** Print {@link missingCollectionsPath}'s refusal and exit 1, or return. */\nexport function refuseMissingCollectionsPath(\n    args: readonly string[],\n    cwd: string,\n    backendDir: string,\n    use: CollectionsPathUse = \"schema\"\n): void {\n    const lines = missingCollectionsPath(args, cwd, backendDir, use);\n    if (!lines) return;\n    console.error(\"\");\n    for (const line of lines) console.error(line);\n    console.error(\"\");\n    process.exit(1);\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;AAoBA,IAAa,wBAAwB;;AAGrC,IAAa,wBAAwB,wDAAwD;;AAG7F,IAAM,oBAAoB,CAAC,iBAAiB,IAAI;;AAGhD,SAAS,qBAAqB,MAAwC;CAClE,KAAK,IAAI,IAAI,GAAG,IAAI,KAAK,QAAQ,KAAK;EAClC,MAAM,QAAQ,KAAK;EACnB,MAAM,KAAK,MAAM,QAAQ,GAAG;EAC5B,IAAI,KAAK,KAAK,kBAAkB,SAAS,MAAM,MAAM,GAAG,EAAE,CAAC,GAAG,OAAO,MAAM,MAAM,KAAK,CAAC,KAAK;EAC5F,IAAI,kBAAkB,SAAS,KAAK,GAAG;GACnC,MAAM,QAAQ,KAAK,IAAI;GACvB,OAAO,SAAS,CAAC,MAAM,WAAW,GAAG,IAAI,QAAQ;EACrD;CACJ;CACA,OAAO;AACX;;;;;;AAOA,IAAM,kCAAkC;CACpC,QAAQ;EACJ;EACA;EACA;CACJ;CACA,SAAS,CACL,4EACA,0CACJ;CACA,QAAQ,CACJ,8EACA,4CACJ;AACJ;;;;;;;;;;;;AAgBA,SAAgB,uBACZ,MACA,KACA,YACA,MAA0B,UACX;CACf,MAAM,QAAQ,qBAAqB,IAAI;CACvC,IAAI,UAAU,MAAM,OAAO;CAC3B,MAAM,WAAW,KAAK,QAAQ,KAAK,KAAK;CACxC,IAAI,GAAG,WAAW,QAAQ,GAAG,OAAO;CAEpC,MAAM,QAAQ;EACV,MAAM,IAAI,kCAAkC,MAAM,EAAE;EACpD,MAAM,KAAK,oBAAoB,UAAU;EACzC,MAAM,KAAK,QAAQ,sBAAsB,IAAI,IAAI,EAAE;CACvD;CACA,MAAM,cAAc,KAAK,QAAQ,YAAY,KAAK;CAClD,IAAI,CAAC,KAAK,WAAW,KAAK,KAAK,GAAG,WAAW,WAAW,GACpD,MAAM,KACF,IACA,MAAM,OAAO,+BAA+B,YAAY,gDAAgD,GACxG,MAAM,OAAO,oFAAoF,KAAK,SAAS,KAAK,WAAW,KAAK,KAAK,CAC7I;CAEJ,MAAM,KAAK,IAAI,GAAG,gCAAgC,IAAI,CAAC,KAAI,SAAQ,MAAM,KAAK,KAAK,MAAM,CAAC,CAAC;CAC3F,OAAO;AACX;;AAGA,SAAgB,6BACZ,MACA,KACA,YACA,MAA0B,UACtB;CACJ,MAAM,QAAQ,uBAAuB,MAAM,KAAK,YAAY,GAAG;CAC/D,IAAI,CAAC,OAAO;CACZ,QAAQ,MAAM,EAAE;CAChB,KAAK,MAAM,QAAQ,OAAO,QAAQ,MAAM,IAAI;CAC5C,QAAQ,MAAM,EAAE;CAChB,QAAQ,KAAK,CAAC;AAClB"}

package/dist/precompress.d.ts

@@ -0,0 +1,17 @@
+/**
+ * A content hash in the name, by the runtime's rule (`isContentHashed` in the
+ * server's `serve-spa.ts`): 8+ base64url characters after the last `-` with a
+ * digit or a capital in them. `index-vgugiqRO.js` is; `vendor-analytics.js` is
+ * not.
+ */
+export declare function isContentHashedName(fileName: string): boolean;
+export interface PrecompressOutcome {
+    /** Files that got at least one sibling. */
+    files: number;
+    /** Their total size, and their siblings'. */
+    bytes: number;
+    brotliBytes: number;
+    gzipBytes: number;
+}
+/** Write `.br` and `.gz` siblings for every hashed, compressible asset under `dir`. */
+export declare function precompressStaticAssets(dir: string): PrecompressOutcome;