naro-cli 0.17.0 → 0.19.0

package/dist/prompt.d.ts

@@ -3,11 +3,25 @@ export interface Prompter {
     ask(question: string): Promise<string>;
     /** Question with hidden echo (secrets). */
     askHidden(question: string): Promise<string>;
-    /** y/N confirmation, defaults to No. */
-    confirm(question: string): Promise<boolean>;
+    /**
+     * y/n confirmation. Enter gives `defaultYes` (No unless said otherwise),
+     * and the hint capitalises that answer: `(y/N)` or `(Y/n)`.
+     */
+    confirm(question: string, options?: {
+        defaultYes?: boolean;
+    }): Promise<boolean>;
     /** Pick one option by number; returns its index. */
     select(question: string, options: string[]): Promise<number>;
 }
+/** The hint after a confirmation, capitalising what Enter answers. */
+export declare function confirmHint(defaultYes: boolean): string;
+/**
+ * Reads a confirmation answer. Enter gives the default. With No as the default
+ * anything but yes is No, as it always was; with Yes as the default only no
+ * declines, and an unreadable answer is null — ask again, because declining
+ * is the costly path there.
+ */
+export declare function readConfirmAnswer(answer: string, defaultYes: boolean): boolean | null;
 export declare function isInteractive(): boolean;
 /** Reads all of stdin — the CI path for piped secret values. */
 export declare function readStdin(): Promise<string>;

package/dist/working-tree.d.ts

@@ -0,0 +1,74 @@
+export interface WorkingTreeCopy {
+    /**
+     * Env files in the working tree that are not in the commit, relative to the
+     * source directory — what the build goes without.
+     */
+    leftOut: string[];
+    /**
+     * Committed env files whose working-tree copy differs or is gone: the build
+     * has the committed version.
+     */
+    committedVersion: string[];
+    /**
+     * Committed env files not written because they would land outside the
+     * checkout — under a directory symlinked out of it, or a symlink pointing
+     * out of it — or where nothing can be found: under a folder link to
+     * nothing, or a symlink that resolves to nothing.
+     */
+    outsideProject: string[];
+    /**
+     * Symlinks not copied because their target is an absolute path, relative
+     * to the source directory (known-issues #176). A git deploy has the link
+     * and not the place it points to, so it cannot follow them either.
+     */
+    absoluteLinks: string[];
+    /**
+     * Relative symlinks not copied because they lead out of the source
+     * directory. A git deploy clones the whole repository, so one between the
+     * repository's folders resolves there; deployed from the repository root
+     * with `--root`, it is inside and kept here too (PR #241 review).
+     */
+    linksOutside: string[];
+    /**
+     * Links whose text stays inside but whose real target does not — a
+     * `self -> .` chain, a loop, `..` up to `/` and back down the source's
+     * absolute path — or cannot be resolved with `..` in the text (PR #243
+     * review). `--root` would not bring them in.
+     */
+    linksElsewhere: string[];
+    /** git could not be run, so no committed env file is known. */
+    gitUnavailable: boolean;
+}
+/**
+ * Copies the local working directory into the build checkout, so uncommitted
+ * changes are deployed — as `git clone` would have laid out the repository.
+ *
+ * Env files are the exception to "uncommitted changes". None is copied from
+ * the working tree; the ones in the commit are written with their committed
+ * content, which is what a git deploy of the same commit builds with. A local
+ * edit to a committed `.env`, one hidden behind `skip-worktree`, one only
+ * staged, and an untracked `.env.local` all stay on the machine. `next build`
+ * reads those files on its own and inlines NEXT_PUBLIC_* into the bundle, and
+ * OpenNext bundles every value they hold into the Worker, so a file copied
+ * here would ship values the developer declined to send. The env consent
+ * prompt is the only way local values reach a build (known-issues #7,
+ * CLI-DEPLOY-011).
+ *
+ * Nothing is written outside the checkout: a directory symlinked out of the
+ * tree would otherwise carry a committed `.env` onto the developer's real
+ * file.
+ *
+ * Nor is anything read from outside it. A symlink whose target is absolute,
+ * or relative but out of the source directory, is left out (known-issues
+ * #176): copied as it is, it led the build to the developer's real files —
+ * whatever the app imports through it is bundled, and an app folder linked
+ * from elsewhere had its own `.env.local` read by `next build`. A git deploy
+ * of the same commit cannot follow an absolute one either: the clone has the
+ * link and not the place it points to. A relative link that stays inside is
+ * kept, so a monorepo's links between its own packages work. "Inside" is
+ * judged on the real path as well as on the link's text, from the source and
+ * again from the checkout: `self -> .` makes `self/..` leave the folder while
+ * it reads as staying in (PR #241 review), and `..` up to `/` and back down
+ * the source's absolute path leads to the source from anywhere (PR #243).
+ */
+export declare function copyWorkingTree(source: string, checkout: string): Promise<WorkingTreeCopy>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "naro-cli",
-  "version": "0.17.0",
+  "version": "0.19.0",
   "type": "module",
   "bin": {
     "naro": "./dist/index.js"
@@ -22,11 +22,11 @@
     }
   },
   "dependencies": {
-    "@opennextjs/cloudflare": "1.20.2",
+    "@opennextjs/cloudflare": "1.20.12",
     "@supabase/supabase-js": "2.112.3",
     "@vercel/frameworks": "3.34.0",
     "vinext": "1.1.0",
-    "wrangler": "4.124.0"
+    "wrangler": "4.148.0"
   },
   "devDependencies": {
     "tsup": "8.5.0",
@@ -34,11 +34,11 @@
     "typescript": "7.0.2",
     "vitest": "3.2.7",
     "naro-js": "0.5.0",
-    "@next-deploy/config": "0.1.0",
+    "@next-deploy/sdk": "0.1.0",
     "@next-deploy/core": "0.1.0",
+    "@next-deploy/config": "0.1.0",
     "@next-deploy/build": "0.1.0",
-    "@next-deploy/data-core": "0.1.0",
-    "@next-deploy/sdk": "0.1.0"
+    "@next-deploy/data-core": "0.1.0"
   },
   "scripts": {
     "build": "tsup && pnpm build:types",