create-eigen-game 0.13.0 → 0.13.1

package/dist/prompt.d.ts

@@ -1,79 +0,0 @@
-/**
- * Every question this CLI asks, in one module so the wording lives together
- * and can be asserted. `cli.ts` is the bin entry and runs `main` on import,
- * which makes anything defined there untestable.
- *
- * The organization prompt is the reason this drops to `@clack/core` rather
- * than using `@clack/prompts`' `text`. The suffix: `flutter create --org X
- * --project-name Y` derives `X.Y`, so the organization is a *prefix*, and the
- * reliable way to say so is to render the rest of the identifier, dimmed,
- * while it is being typed. `text` has no hook for that; a custom `TextPrompt`
- * render returns a string, so it does.
- *
- * Everything else comes from `@clack/prompts` rather than being drawn here.
- * Its symbols are exported for exactly this, and they are not constants: each
- * falls back to ASCII on a terminal that cannot show the box-drawing
- * characters, which a hand-typed `│` cannot do.
- */
-import type { Readable, Writable } from "node:stream";
-import type { PackageManager } from "./index.js";
-/**
- * Where a question reads its answer from. Parameters for the same reason every
- * clack prompt takes them: a prompt is otherwise the one part of a CLI that
- * cannot be driven by a test.
- */
-export interface Io {
-    input?: Readable;
-    output?: Writable;
-}
-/**
- * Two or more dot-separated Java identifiers. `flutter create --org` accepts
- * anything and defers the complaint to Gradle, which reports it as a manifest
- * error in a generated file, so `com.example-games` costs a full scaffold and
- * a first build before anyone learns that a hyphen is not legal in a package
- * segment.
- */
-export declare const ORG: RegExp;
-/** The default, which an empty answer accepts. */
-export declare const DEFAULT_ORG = "com.example";
-/** A `com.acme.chess` answer to a game called `chess`, which yields `com.acme.chess.chess`. */
-export declare function repeatsGameName(org: string, game: string): boolean;
-/** The organization implied by an answer that already ends in the game name. */
-export declare function withoutGameName(org: string): string | undefined;
-/**
- * Asks, with the game name rendered dimmed after the cursor so the shape of
- * the answer is visible while it is being given.
- *
- * Returns the organization, `undefined` for the default, or `null` when
- * cancelled.
- *
- * `input` and `output` default to this process's, and are parameters for the
- * same reason every clack prompt takes them: a prompt is otherwise the one
- * part of a CLI that cannot be driven by a test.
- */
-export declare function askForOrg(game: string, registering: boolean, io?: Io): Promise<string | undefined | null>;
-/**
- * Asked only when {@link firebaseReadiness} found something missing, and
- * defaulted to "no" because the honest answer usually is: the tools are two
- * commands away, and the alternative is an app that throws at launch until
- * they are installed anyway.
- */
-export declare function askToScaffoldWithoutFirebase(io?: Io): Promise<boolean | null>;
-/** Defaulted to yes: the scaffold is a few hundred generated files, and a commit is what makes the first `git diff` the first game change rather than all of them. */
-export declare function askForGit(io?: Io): Promise<boolean | null>;
-/**
- * Defaulted to no, and the hint says why rather than leaving it as an
- * arbitrary-looking choice: `release.yml` needs an upload keystore and a Play
- * service account, so a project that takes the workflows before it has either
- * gets a red `main` from its first push.
- */
-export declare function askForWorkflows(io?: Io): Promise<boolean | null>;
-/**
- * The package manager, asked only when nothing else could say.
- *
- * `npm create` and `pnpm create` both set `npm_config_user_agent`, so this is
- * reached by the paths that do not: a global install, or running the binary
- * directly. Rare, but it decides what every generated script says, and the old
- * silent fallback to pnpm was a guess printed into a project's package.json.
- */
-export declare function askForPackageManager(io?: Io): Promise<PackageManager | null>;

package/dist/summary.d.ts

@@ -1,26 +0,0 @@
-/**
- * The closing summary, and the only output of a scaffold anyone reads.
- *
- * A run drives several tools with plenty to say, so where the project went,
- * what to edit, and what to run are worth restating at the bottom. Returned in
- * pieces rather than as one block, because the CLI renders each in a different
- * shape: the outcomes as status lines, the commands as a boxed note, the
- * destination as the closing line.
- *
- * Its own module so it can be asserted: `cli.ts` is the bin entry and runs
- * `main` on import, which makes anything defined there untestable. The package
- * `exports` map does not expose this, so it is internal despite being
- * importable by the tests.
- */
-import type { PackageManager, ScaffoldResult } from "./index.js";
-export interface Summary {
-    /** What became of the repository and of Firebase, when there is something to say. */
-    status: string[];
-    /** The commands worth having, as one block. */
-    next: string;
-    /** One-line asides, after the block. */
-    footnotes: string[];
-    /** The closing line. */
-    headline: string;
-}
-export declare function summarise(result: ScaffoldResult, manager: PackageManager, workflows: boolean): Summary;