@bitvea/feedback-cli 1.0.0

package/dist/commands/register.js

@@ -0,0 +1,125 @@
+// `feedback-toolbar register` - make sure this deployment exists as a project.
+//
+// A first-class command, not a step inside `init`, and issues #11 and #17 both
+// needed it to be:
+//
+//   - #11 reopened because `init` runs on a laptop, where VERCEL_URL does not
+//     exist, so the project URL was undefined and registration was silently
+//     skipped. The fix is to register where those variables DO exist: in the
+//     build. `init` wires this command in as a prebuild step.
+//   - #17 added the script-tag install, which has no build to hook at all. Its
+//     project is registered by running this command once from a terminal or CI.
+//
+// Both callers want the same three things: resolve where the values come from,
+// call the one registration service, and say clearly what happened. None of
+// them wants a second opinion on what a valid URL is - see ./registration.ts.
+import { RegistrationError, postRegistration, } from "../registration.js";
+/** Where `--api-url` falls back to. The public name is what a build already has. */
+export const API_URL_ENV_VARS = [
+    "NEXT_PUBLIC_FEEDBACK_TOOLBAR_API_URL",
+    "FEEDBACK_TOOLBAR_API_URL",
+];
+/**
+ * Where `--api-key` falls back to, and the only place a key is ever read from.
+ * Never a file, never a `data-` attribute, never an argument this CLI writes
+ * down: a deploy key's whole power is creating projects, so it lives in the
+ * build environment and nowhere else.
+ */
+export const API_KEY_ENV_VAR = "FEEDBACK_TOOLBAR_API_KEY";
+/**
+ * Register the deployment, or confirm it is already registered.
+ *
+ * Idempotent because the backend is: the second call with the same normalised
+ * URL is a no-op that answers `created: false`. That is what makes this safe
+ * as a prebuild step, which runs on every deploy forever.
+ *
+ * Throws `RegistrationError` with a message naming the missing piece when it
+ * cannot proceed. It never guesses: a registration under a URL nobody meant
+ * creates a project that collects feedback from a page that does not exist.
+ */
+export async function register(options) {
+    const { env } = options;
+    const transport = options.registerProject ?? postRegistration;
+    const apiUrl = options.apiUrl ?? API_URL_ENV_VARS.map((name) => env[name]).find(Boolean);
+    if (!apiUrl) {
+        throw new RegistrationError("no backend URL. Pass --api-url https://feedback.bitvea.com, or set " +
+            `${API_URL_ENV_VARS[0]} in the build environment (\`init\` writes it into .env.local).`);
+    }
+    const apiKey = options.apiKey ?? env[API_KEY_ENV_VAR];
+    if (!apiKey) {
+        throw new RegistrationError(`no deploy key. Pass --api-key, or set ${API_KEY_ENV_VAR} in the build ` +
+            "environment. Create one in the dashboard under Settings > Deploy keys. " +
+            "It must never be committed or put in a page.");
+    }
+    const projectUrl = options.projectUrl ?? inferProjectUrl(env);
+    if (!projectUrl) {
+        throw new RegistrationError("could not tell which URL to register. Pass --project-url https://myapp.com. " +
+            "Inside a Vercel build this is read from VERCEL_PROJECT_PRODUCTION_URL or " +
+            "VERCEL_URL, neither of which is set here.");
+    }
+    const { created, project } = await transport({
+        apiUrl,
+        apiKey,
+        projectUrl,
+        repoOwner: env.VERCEL_GIT_REPO_OWNER,
+        repoSlug: env.VERCEL_GIT_REPO_SLUG,
+        packageName: options.packageName,
+        // Undefined rather than an empty array off Vercel: "I have nothing to
+        // report" and "I report an empty list" are the same thing here, and the
+        // shorter one keeps the request the shape it has always had.
+        origins: emptyToUndefined(inferProjectOrigins(env)),
+    });
+    return { projectUrl, created, projectName: project?.name };
+}
+/**
+ * The URL to register the project under, from the build environment.
+ *
+ * Same precedence as the toolbar's own `resolveConfig`, and that agreement is
+ * the point: the toolbar reports this value back at runtime, so if the two
+ * picked differently the lookup would miss on every preview deployment. The
+ * production hostname wins because a preview URL changes on every commit, and
+ * keying on it would create a project per deploy instead of collecting a
+ * project's feedback in one place.
+ */
+export function inferProjectUrl(env) {
+    const host = env.VERCEL_PROJECT_PRODUCTION_URL ?? env.VERCEL_URL;
+    return host ? `https://${host}` : undefined;
+}
+/**
+ * The browser origins this deployment serves the toolbar from.
+ *
+ * A DIFFERENT question from `inferProjectUrl`, and conflating them is what
+ * made the toolbar unusable everywhere it was installed. That function answers
+ * "which project is this", and answers it with the production URL because a
+ * project's feedback has to collect in one place across every deploy. This one
+ * answers "where will a browser be calling us from", and on a Vercel install
+ * the answer is never the production URL: the toolbar is off in production by
+ * design, so it only ever runs on a preview, whose origin is per-branch or
+ * per-commit.
+ *
+ * Both are reported, in this order:
+ *
+ *   - `VERCEL_BRANCH_URL` - `<project>-git-<branch>-<team>.vercel.app`. Stable
+ *     for the life of the branch, and the URL a reviewer is actually sent, so
+ *     it is the one that matters. It is also bounded by branch count rather
+ *     than by deploy count, which is what keeps the allow-list from growing
+ *     without limit.
+ *   - `VERCEL_URL` - this deployment alone. Included because a reviewer handed
+ *     a specific deployment's URL is a real case, and because a build with no
+ *     branch alias (a `vercel deploy` from a terminal) has nothing else.
+ *
+ * Empty off Vercel, where neither exists and there is no preview to allow.
+ * The backend normalises and de-duplicates, and drops the project's own URL,
+ * so this does not have to be careful about overlap - only about never
+ * inventing a host it was not told.
+ */
+export function inferProjectOrigins(env) {
+    const hosts = [env.VERCEL_BRANCH_URL, env.VERCEL_URL];
+    return hosts
+        .filter((host) => Boolean(host))
+        .map((host) => `https://${host}`);
+}
+function emptyToUndefined(values) {
+    return values.length > 0 ? values : undefined;
+}
+//# sourceMappingURL=register.js.map

package/dist/commands/register.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"register.js","sourceRoot":"","sources":["../../src/commands/register.ts"],"names":[],"mappings":"AAAA,+EAA+E;AAC/E,EAAE;AACF,+EAA+E;AAC/E,mBAAmB;AACnB,EAAE;AACF,8EAA8E;AAC9E,4EAA4E;AAC5E,6EAA6E;AAC7E,8DAA8D;AAC9D,+EAA+E;AAC/E,gFAAgF;AAChF,EAAE;AACF,+EAA+E;AAC/E,4EAA4E;AAC5E,8EAA8E;AAC9E,OAAO,EACL,iBAAiB,EACjB,gBAAgB,GAEjB,MAAM,iBAAiB,CAAC;AAEzB,oFAAoF;AACpF,MAAM,CAAC,MAAM,gBAAgB,GAAG;IAC9B,sCAAsC;IACtC,0BAA0B;CAClB,CAAC;AAEX;;;;;GAKG;AACH,MAAM,CAAC,MAAM,eAAe,GAAG,0BAA0B,CAAC;AAyB1D;;;;;;;;;;GAUG;AACH,MAAM,CAAC,KAAK,UAAU,QAAQ,CAC5B,OAAwB;IAExB,MAAM,EAAE,GAAG,EAAE,GAAG,OAAO,CAAC;IACxB,MAAM,SAAS,GAAG,OAAO,CAAC,eAAe,IAAI,gBAAgB,CAAC;IAE9D,MAAM,MAAM,GACV,OAAO,CAAC,MAAM,IAAI,gBAAgB,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;IAC5E,IAAI,CAAC,MAAM,EAAE,CAAC;QACZ,MAAM,IAAI,iBAAiB,CACzB,qEAAqE;YACnE,GAAG,gBAAgB,CAAC,CAAC,CAAC,iEAAiE,CAC1F,CAAC;IACJ,CAAC;IAED,MAAM,MAAM,GAAG,OAAO,CAAC,MAAM,IAAI,GAAG,CAAC,eAAe,CAAC,CAAC;IACtD,IAAI,CAAC,MAAM,EAAE,CAAC;QACZ,MAAM,IAAI,iBAAiB,CACzB,yCAAyC,eAAe,gBAAgB;YACtE,yEAAyE;YACzE,8CAA8C,CACjD,CAAC;IACJ,CAAC;IAED,MAAM,UAAU,GAAG,OAAO,CAAC,UAAU,IAAI,eAAe,CAAC,GAAG,CAAC,CAAC;IAC9D,IAAI,CAAC,UAAU,EAAE,CAAC;QAChB,MAAM,IAAI,iBAAiB,CACzB,8EAA8E;YAC5E,2EAA2E;YAC3E,2CAA2C,CAC9C,CAAC;IACJ,CAAC;IAED,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,GAAG,MAAM,SAAS,CAAC;QAC3C,MAAM;QACN,MAAM;QACN,UAAU;QACV,SAAS,EAAE,GAAG,CAAC,qBAAqB;QACpC,QAAQ,EAAE,GAAG,CAAC,oBAAoB;QAClC,WAAW,EAAE,OAAO,CAAC,WAAW;QAChC,sEAAsE;QACtE,wEAAwE;QACxE,6DAA6D;QAC7D,OAAO,EAAE,gBAAgB,CAAC,mBAAmB,CAAC,GAAG,CAAC,CAAC;KACpD,CAAC,CAAC;IAEH,OAAO,EAAE,UAAU,EAAE,OAAO,EAAE,WAAW,EAAE,OAAO,EAAE,IAAI,EAAE,CAAC;AAC7D,CAAC;AAED;;;;;;;;;GASG;AACH,MAAM,UAAU,eAAe,CAC7B,GAAuC;IAEvC,MAAM,IAAI,GAAG,GAAG,CAAC,6BAA6B,IAAI,GAAG,CAAC,UAAU,CAAC;IACjE,OAAO,IAAI,CAAC,CAAC,CAAC,WAAW,IAAI,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC;AAC9C,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,MAAM,UAAU,mBAAmB,CACjC,GAAuC;IAEvC,MAAM,KAAK,GAAG,CAAC,GAAG,CAAC,iBAAiB,EAAE,GAAG,CAAC,UAAU,CAAC,CAAC;IACtD,OAAO,KAAK;SACT,MAAM,CAAC,CAAC,IAAI,EAAkB,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;SAC/C,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,WAAW,IAAI,EAAE,CAAC,CAAC;AACtC,CAAC;AAED,SAAS,gBAAgB,CAAC,MAAgB;IACxC,OAAO,MAAM,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,SAAS,CAAC;AAChD,CAAC"}

package/dist/index.d.ts

@@ -0,0 +1,2 @@
+export { run, type RunOptions } from "./run.js";
+//# sourceMappingURL=index.d.ts.map

package/dist/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAOA,OAAO,EAAE,GAAG,EAAE,KAAK,UAAU,EAAE,MAAM,OAAO,CAAC"}

package/dist/index.js

@@ -0,0 +1,9 @@
+// The package's public surface, and it is deliberately one function.
+//
+// `@bitvea/feedback-toolbar`'s bin imports `run` and calls it in its own
+// process, which is what makes `npx @bitvea/feedback-toolbar init` and the
+// `prebuild` line committed in customers' repositories behave exactly as they
+// did when the installer lived in that package. Anything else exported from
+// here would be a second contract to keep across two release lines.
+export { run } from "./run.js";
+//# sourceMappingURL=index.js.map

package/dist/index.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA,qEAAqE;AACrE,EAAE;AACF,yEAAyE;AACzE,2EAA2E;AAC3E,8EAA8E;AAC9E,4EAA4E;AAC5E,oEAAoE;AACpE,OAAO,EAAE,GAAG,EAAmB,MAAM,OAAO,CAAC"}

package/dist/install/env.d.ts

@@ -0,0 +1,2 @@
+export declare const API_URL_ENV_VAR = "NEXT_PUBLIC_FEEDBACK_TOOLBAR_API_URL";
+//# sourceMappingURL=env.d.ts.map

package/dist/install/env.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"env.d.ts","sourceRoot":"","sources":["../../src/install/env.ts"],"names":[],"mappings":"AAiBA,eAAO,MAAM,eAAe,yCAAyC,CAAC"}

package/dist/install/env.js

@@ -0,0 +1,19 @@
+// The environment-variable names this installer writes, and who reads them.
+//
+// These are a contract between two artefacts that no longer share a package:
+// the CLI writes `NEXT_PUBLIC_FEEDBACK_TOOLBAR_API_URL`, and
+// `packages/toolbar/src/config.ts` reads it back out of the host's build. The
+// literal is duplicated here rather than imported, because an import would be
+// a `@bitvea/*` specifier in this package's emitted dist/ - the one thing that
+// would stop the published tarball standing on its own with no node_modules
+// at all, which is the strongest assertion its publishable check makes.
+//
+// Duplication that nobody checks is drift, and drift here is the class of
+// silent failure the install path is already full of: a variable written under
+// one name and read under another produces a toolbar that mounts and never
+// works. So `env.test.ts` reads packages/toolbar/src/config.ts off disk and
+// asserts the two strings match. That test is monorepo-only and fails loudly
+// if the file moves, which is the correct behaviour: the pair has to be looked
+// at together.
+export const API_URL_ENV_VAR = "NEXT_PUBLIC_FEEDBACK_TOOLBAR_API_URL";
+//# sourceMappingURL=env.js.map

package/dist/install/env.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"env.js","sourceRoot":"","sources":["../../src/install/env.ts"],"names":[],"mappings":"AAAA,4EAA4E;AAC5E,EAAE;AACF,6EAA6E;AAC7E,6DAA6D;AAC7D,8EAA8E;AAC9E,8EAA8E;AAC9E,+EAA+E;AAC/E,4EAA4E;AAC5E,wEAAwE;AACxE,EAAE;AACF,0EAA0E;AAC1E,+EAA+E;AAC/E,2EAA2E;AAC3E,4EAA4E;AAC5E,6EAA6E;AAC7E,+EAA+E;AAC/E,eAAe;AACf,MAAM,CAAC,MAAM,eAAe,GAAG,sCAAsC,CAAC"}

package/dist/install/fs.d.ts

@@ -0,0 +1,16 @@
+export interface InstallerFs {
+    exists(path: string): boolean;
+    readFile(path: string): string;
+    writeFile(path: string, contents: string): void;
+}
+/** An in-memory tree, which is what the installer's tests run against. */
+export declare class MemoryFs implements InstallerFs {
+    readonly files: Map<string, string>;
+    constructor(files?: Record<string, string>);
+    exists(path: string): boolean;
+    readFile(path: string): string;
+    writeFile(path: string, contents: string): void;
+}
+/** Join path segments with `/`, collapsing the duplicates that creep in. */
+export declare function joinPath(...parts: string[]): string;
+//# sourceMappingURL=fs.d.ts.map

package/dist/install/fs.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"fs.d.ts","sourceRoot":"","sources":["../../src/install/fs.ts"],"names":[],"mappings":"AAOA,MAAM,WAAW,WAAW;IAC1B,MAAM,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC;IAC9B,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAAC;IAC/B,SAAS,CAAC,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,IAAI,CAAC;CACjD;AAED,0EAA0E;AAC1E,qBAAa,QAAS,YAAW,WAAW;IAC1C,QAAQ,CAAC,KAAK,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;gBAExB,KAAK,GAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAM;IAI9C,MAAM,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO;IAI7B,QAAQ,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM;IAM9B,SAAS,CAAC,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,IAAI;CAGhD;AAED,4EAA4E;AAC5E,wBAAgB,QAAQ,CAAC,GAAG,KAAK,EAAE,MAAM,EAAE,GAAG,MAAM,CAKnD"}

package/dist/install/fs.js

@@ -0,0 +1,33 @@
+// The filesystem the installer talks to, as an interface.
+//
+// The installer edits somebody else's repository, so its tests need to run
+// against a tree they fully control, and a codemod tested only against the
+// real disk is a codemod nobody dares change. Everything below the interface
+// is a handful of thin wrappers; everything above it is pure logic.
+/** An in-memory tree, which is what the installer's tests run against. */
+export class MemoryFs {
+    files;
+    constructor(files = {}) {
+        this.files = new Map(Object.entries(files));
+    }
+    exists(path) {
+        return this.files.has(path);
+    }
+    readFile(path) {
+        const contents = this.files.get(path);
+        if (contents === undefined)
+            throw new Error(`no such file: ${path}`);
+        return contents;
+    }
+    writeFile(path, contents) {
+        this.files.set(path, contents);
+    }
+}
+/** Join path segments with `/`, collapsing the duplicates that creep in. */
+export function joinPath(...parts) {
+    return parts
+        .filter((p) => p.length > 0)
+        .join("/")
+        .replace(/\/{2,}/g, "/");
+}
+//# sourceMappingURL=fs.js.map

package/dist/install/fs.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"fs.js","sourceRoot":"","sources":["../../src/install/fs.ts"],"names":[],"mappings":"AAAA,0DAA0D;AAC1D,EAAE;AACF,2EAA2E;AAC3E,2EAA2E;AAC3E,6EAA6E;AAC7E,oEAAoE;AAQpE,0EAA0E;AAC1E,MAAM,OAAO,QAAQ;IACV,KAAK,CAAsB;IAEpC,YAAY,QAAgC,EAAE;QAC5C,IAAI,CAAC,KAAK,GAAG,IAAI,GAAG,CAAC,MAAM,CAAC,OAAO,CAAC,KAAK,CAAC,CAAC,CAAC;IAC9C,CAAC;IAED,MAAM,CAAC,IAAY;QACjB,OAAO,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;IAC9B,CAAC;IAED,QAAQ,CAAC,IAAY;QACnB,MAAM,QAAQ,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QACtC,IAAI,QAAQ,KAAK,SAAS;YAAE,MAAM,IAAI,KAAK,CAAC,iBAAiB,IAAI,EAAE,CAAC,CAAC;QACrE,OAAO,QAAQ,CAAC;IAClB,CAAC;IAED,SAAS,CAAC,IAAY,EAAE,QAAgB;QACtC,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,QAAQ,CAAC,CAAC;IACjC,CAAC;CACF;AAED,4EAA4E;AAC5E,MAAM,UAAU,QAAQ,CAAC,GAAG,KAAe;IACzC,OAAO,KAAK;SACT,MAAM,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,MAAM,GAAG,CAAC,CAAC;SAC3B,IAAI,CAAC,GAAG,CAAC;SACT,OAAO,CAAC,SAAS,EAAE,GAAG,CAAC,CAAC;AAC7B,CAAC"}

package/dist/install/strategies.d.ts

@@ -0,0 +1,109 @@
+import { type InstallerFs } from "./fs.js";
+/**
+ * The package `init` writes into a host app's dependencies and imports from in
+ * their layout.
+ *
+ * It is the name of a DIFFERENT package from this one, and that is the point:
+ * it is data this installer writes into somebody else's repository, never a
+ * module specifier. Nothing here imports the toolbar, and nothing here may -
+ * an emitted `@bitvea/*` specifier is what would stop this tarball standing on
+ * its own with no node_modules at all.
+ */
+export declare const PACKAGE_NAME = "@bitvea/feedback-toolbar";
+export declare const COMPONENT_NAME = "FeedbackToolbar";
+/** The file the script-tag route is served as, relative to the backend URL. */
+export declare const SCRIPT_BUNDLE_PATH = "/toolbar.js";
+export interface InjectionSite {
+    /** The file to edit. */
+    path: string;
+    /** Human-readable description of what was found, for the CLI's output. */
+    description: string;
+}
+/**
+ * How a strategy's host app gets the toolbar's *code*, which decides which of
+ * the installer's other steps apply at all.
+ *
+ * `npm-package`: the toolbar is a dependency the host's bundler compiles, so
+ * the install needs a package.json entry, an env var for the API URL, and a
+ * prebuild hook to register the project from the build.
+ *
+ * `script-tag`: the toolbar is a file served from the backend and configured
+ * from `data-` attributes on the tag. There is no dependency to add, no env
+ * file to read at runtime, and - the reason #17 called this out - no build to
+ * hook, so its project is registered by running `register` by hand.
+ */
+export type Delivery = "npm-package" | "script-tag";
+/**
+ * The environment a script-tag install declares, when the developer has not
+ * said otherwise.
+ *
+ * The gate treats "absent" as off, and a static HTML file cannot know which
+ * deployment served it - so a tag with no `data-environment` mounts nothing,
+ * ever. That is the correct default for a value we could only guess, and the
+ * wrong default for an installer whose whole job is to leave a working
+ * install behind: #17 asks for a toolbar that mounts on a plain page with no
+ * build step, and a tag the developer has to hand-edit is not that.
+ *
+ * So `init` writes an environment, and the value is a review environment
+ * because installing a review tool on a page is what the command means. The
+ * result is printed as a change and called out as a note, and `--environment`
+ * overrides it - including with `production`, which is how somebody turns the
+ * tag off without removing it.
+ */
+export declare const DEFAULT_SCRIPT_ENVIRONMENT = "preview";
+/** What `inject` needs to know about the install to write the markup. */
+export interface InjectionContext {
+    /** Base URL of the BitVea Feedback backend, no trailing slash. */
+    apiUrl: string;
+    /** The deployment URL the project is registered under, when known. */
+    projectUrl?: string | undefined;
+    /**
+     * What the injected markup declares as its environment. Only the script-tag
+     * route uses it: an npm install resolves the environment from whatever its
+     * host's build populates - see buildEnv.ts - and a static page has no build
+     * provider to be resolved from at all.
+     */
+    environment?: string | undefined;
+}
+export interface InjectionStrategy {
+    /** Stable id, reported in the CLI's output. */
+    readonly id: string;
+    readonly label: string;
+    /** Which of the installer's steps apply. Defaults to `npm-package`. */
+    readonly delivery?: Delivery;
+    /** Find the file to inject into, or null when this strategy does not apply. */
+    detect(fs: InstallerFs, root: string): InjectionSite | null;
+    /** True when the provider is already there, which makes a re-run a no-op. */
+    isInstalled(source: string): boolean;
+    /**
+     * Return the edited source. Only called when `isInstalled` is false, and
+     * throws when it cannot do the edit, so a partial write is not possible:
+     * the caller writes only what this returns.
+     */
+    inject(source: string, context: InjectionContext): string;
+}
+export declare const nextAppRouterStrategy: InjectionStrategy;
+/**
+ * The `<script src>` install, for an app with no build step to add a
+ * dependency to. Second in the list on purpose: an App Router app usually
+ * also has an index.html somewhere, and the npm install is the better one.
+ *
+ * Note what the injected tag does NOT carry: a deploy key. There is no
+ * supported way to put one in a page, and the bundle refuses to mount when it
+ * finds anything that looks like one - a key in a page is a key in every
+ * visitor's hands, and its whole power is creating projects.
+ *
+ * It does carry an environment, and it has to. A static file cannot know which
+ * deployment served it and the gate treats absent as off, so a tag without one
+ * mounts nothing at all - which is what #17's "mounts a working toolbar on a
+ * plain HTML page" cannot mean. The value is written, printed as a change, and
+ * called out as a note; `--environment production` is how a developer turns
+ * the tag off without deleting it. See DEFAULT_SCRIPT_ENVIRONMENT.
+ */
+export declare const htmlScriptTagStrategy: InjectionStrategy;
+/** A failure the developer can act on, as opposed to an internal error. */
+export declare class InjectionError extends Error {
+    constructor(message: string);
+}
+export declare const STRATEGIES: readonly InjectionStrategy[];
+//# sourceMappingURL=strategies.d.ts.map

package/dist/install/strategies.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"strategies.d.ts","sourceRoot":"","sources":["../../src/install/strategies.ts"],"names":[],"mappings":"AAOA,OAAO,EAAY,KAAK,WAAW,EAAE,MAAM,MAAM,CAAC;AAElD;;;;;;;;;GASG;AACH,eAAO,MAAM,YAAY,6BAA6B,CAAC;AACvD,eAAO,MAAM,cAAc,oBAAoB,CAAC;AAEhD,+EAA+E;AAC/E,eAAO,MAAM,kBAAkB,gBAAgB,CAAC;AAEhD,MAAM,WAAW,aAAa;IAC5B,wBAAwB;IACxB,IAAI,EAAE,MAAM,CAAC;IACb,0EAA0E;IAC1E,WAAW,EAAE,MAAM,CAAC;CACrB;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,MAAM,QAAQ,GAAG,aAAa,GAAG,YAAY,CAAC;AAEpD;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,0BAA0B,YAAY,CAAC;AAEpD,yEAAyE;AACzE,MAAM,WAAW,gBAAgB;IAC/B,kEAAkE;IAClE,MAAM,EAAE,MAAM,CAAC;IACf,sEAAsE;IACtE,UAAU,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAChC;;;;;OAKG;IACH,WAAW,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;CAClC;AAED,MAAM,WAAW,iBAAiB;IAChC,+CAA+C;IAC/C,QAAQ,CAAC,EAAE,EAAE,MAAM,CAAC;IACpB,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;IACvB,uEAAuE;IACvE,QAAQ,CAAC,QAAQ,CAAC,EAAE,QAAQ,CAAC;IAC7B,+EAA+E;IAC/E,MAAM,CAAC,EAAE,EAAE,WAAW,EAAE,IAAI,EAAE,MAAM,GAAG,aAAa,GAAG,IAAI,CAAC;IAC5D,6EAA6E;IAC7E,WAAW,CAAC,MAAM,EAAE,MAAM,GAAG,OAAO,CAAC;IACrC;;;;OAIG;IACH,MAAM,CAAC,MAAM,EAAE,MAAM,EAAE,OAAO,EAAE,gBAAgB,GAAG,MAAM,CAAC;CAC3D;AAUD,eAAO,MAAM,qBAAqB,EAAE,iBAwDnC,CAAC;AAKF;;;;;;;;;;;;;;;;GAgBG;AACH,eAAO,MAAM,qBAAqB,EAAE,iBAuCnC,CAAC;AAgEF,2EAA2E;AAC3E,qBAAa,cAAe,SAAQ,KAAK;gBAC3B,OAAO,EAAE,MAAM;CAI5B;AAED,eAAO,MAAM,UAAU,EAAE,SAAS,iBAAiB,EAGlD,CAAC"}

package/dist/install/strategies.js

@@ -0,0 +1,208 @@
+// How the provider gets into a host app, one strategy per install path.
+//
+// The spec asks for this explicitly: another framework, or another way of
+// mounting into Next.js, should be a new strategy rather than a rewrite of the
+// injector. So the orchestration in `init.ts` knows only this interface, and
+// the one strategy that exists here knows only App Router layouts.
+import { joinPath } from "./fs.js";
+/**
+ * The package `init` writes into a host app's dependencies and imports from in
+ * their layout.
+ *
+ * It is the name of a DIFFERENT package from this one, and that is the point:
+ * it is data this installer writes into somebody else's repository, never a
+ * module specifier. Nothing here imports the toolbar, and nothing here may -
+ * an emitted `@bitvea/*` specifier is what would stop this tarball standing on
+ * its own with no node_modules at all.
+ */
+export const PACKAGE_NAME = "@bitvea/feedback-toolbar";
+export const COMPONENT_NAME = "FeedbackToolbar";
+/** The file the script-tag route is served as, relative to the backend URL. */
+export const SCRIPT_BUNDLE_PATH = "/toolbar.js";
+/**
+ * The environment a script-tag install declares, when the developer has not
+ * said otherwise.
+ *
+ * The gate treats "absent" as off, and a static HTML file cannot know which
+ * deployment served it - so a tag with no `data-environment` mounts nothing,
+ * ever. That is the correct default for a value we could only guess, and the
+ * wrong default for an installer whose whole job is to leave a working
+ * install behind: #17 asks for a toolbar that mounts on a plain page with no
+ * build step, and a tag the developer has to hand-edit is not that.
+ *
+ * So `init` writes an environment, and the value is a review environment
+ * because installing a review tool on a page is what the command means. The
+ * result is printed as a change and called out as a note, and `--environment`
+ * overrides it - including with `production`, which is how somebody turns the
+ * tag off without removing it.
+ */
+export const DEFAULT_SCRIPT_ENVIRONMENT = "preview";
+/** Where an App Router root layout lives, most conventional first. */
+const APP_ROUTER_LAYOUTS = [
+    "app/layout.tsx",
+    "src/app/layout.tsx",
+    "app/layout.jsx",
+    "src/app/layout.jsx",
+];
+export const nextAppRouterStrategy = {
+    id: "next-app-router",
+    label: "Next.js App Router",
+    delivery: "npm-package",
+    detect(fs, root) {
+        for (const candidate of APP_ROUTER_LAYOUTS) {
+            const path = joinPath(root, candidate);
+            if (fs.exists(path)) {
+                return { path, description: `root layout at ${candidate}` };
+            }
+        }
+        return null;
+    },
+    isInstalled(source) {
+        // Both halves, because a half-installed file is what a failed earlier run
+        // would leave and re-running should finish it rather than skip it.
+        return (source.includes(PACKAGE_NAME) && source.includes(`<${COMPONENT_NAME}`));
+    },
+    inject(source, context) {
+        let out = source;
+        if (!out.includes(PACKAGE_NAME)) {
+            out = addImport(out);
+        }
+        if (!out.includes(`<${COMPONENT_NAME}`)) {
+            // The API URL goes in the MARKUP, not only into an env file, and that is
+            // the difference between an install that works after a deploy and one
+            // that silently does nothing.
+            //
+            // `init` writes `NEXT_PUBLIC_FEEDBACK_TOOLBAR_API_URL` into `.env.local`,
+            // which create-next-app gitignores - so on the host's next deploy the
+            // variable does not exist, `resolveConfig` leaves `enabled` false, and
+            // the deployed toolbar renders nothing. The developer sees no toolbar and
+            // no error, and nothing in the install told them to add the variable to
+            // their hosting provider by hand.
+            //
+            // The value is not a secret - it is a `NEXT_PUBLIC_` URL, and the
+            // script-tag route already writes the same value into a page - so
+            // committing it is exactly right. `resolveConfig` lets a prop beat the
+            // environment, which is what makes this deterministic; a developer who
+            // wants a different backend per environment deletes the prop and sets
+            // the variable in their hosting provider instead.
+            out = insertBeforeClosingBody(out, `<${COMPONENT_NAME} apiUrl="${context.apiUrl}" />`);
+        }
+        return out;
+    },
+};
+/** Where a plain HTML entry point lives, most conventional first. */
+const HTML_ENTRY_FILES = ["index.html", "public/index.html", "src/index.html"];
+/**
+ * The `<script src>` install, for an app with no build step to add a
+ * dependency to. Second in the list on purpose: an App Router app usually
+ * also has an index.html somewhere, and the npm install is the better one.
+ *
+ * Note what the injected tag does NOT carry: a deploy key. There is no
+ * supported way to put one in a page, and the bundle refuses to mount when it
+ * finds anything that looks like one - a key in a page is a key in every
+ * visitor's hands, and its whole power is creating projects.
+ *
+ * It does carry an environment, and it has to. A static file cannot know which
+ * deployment served it and the gate treats absent as off, so a tag without one
+ * mounts nothing at all - which is what #17's "mounts a working toolbar on a
+ * plain HTML page" cannot mean. The value is written, printed as a change, and
+ * called out as a note; `--environment production` is how a developer turns
+ * the tag off without deleting it. See DEFAULT_SCRIPT_ENVIRONMENT.
+ */
+export const htmlScriptTagStrategy = {
+    id: "html-script-tag",
+    label: "plain HTML page",
+    delivery: "script-tag",
+    detect(fs, root) {
+        for (const candidate of HTML_ENTRY_FILES) {
+            const path = joinPath(root, candidate);
+            if (fs.exists(path)) {
+                return { path, description: `HTML page at ${candidate}` };
+            }
+        }
+        return null;
+    },
+    isInstalled(source) {
+        return source.includes(SCRIPT_BUNDLE_PATH);
+    },
+    inject(source, context) {
+        if (!context.projectUrl) {
+            // Unlike the npm route, this one cannot fall back to reading the URL
+            // from the environment at runtime: a static page has no environment.
+            // Without it the toolbar would ask the backend about a project keyed on
+            // the empty string, so refuse rather than install something inert.
+            throw new InjectionError("a script-tag install needs the project's URL, and nothing here reports one.\n" +
+                "Re-run with --project-url https://myapp.com.");
+        }
+        const environment = context.environment ?? DEFAULT_SCRIPT_ENVIRONMENT;
+        return insertBeforeClosingBody(source, `<script src="${context.apiUrl}${SCRIPT_BUNDLE_PATH}" ` +
+            `data-api-url="${context.apiUrl}" ` +
+            `data-project-url="${context.projectUrl}" ` +
+            `data-environment="${environment}" defer></script>`);
+    },
+};
+function addImport(source) {
+    const importLine = `import { ${COMPONENT_NAME} } from "${PACKAGE_NAME}";\n`;
+    // After the last top-level import, so the file keeps its import block
+    // together rather than growing a stray line above a directive.
+    const importRe = /^import[\s\S]*?;[ \t]*$/gm;
+    let lastEnd = -1;
+    for (const match of source.matchAll(importRe)) {
+        lastEnd = match.index + match[0].length;
+    }
+    if (lastEnd >= 0) {
+        return `${source.slice(0, lastEnd)}\n${importLine.trimEnd()}${source.slice(lastEnd)}`;
+    }
+    // No imports at all: go after a leading "use client" directive if present,
+    // since nothing may precede one.
+    const directive = /^\s*("use client"|'use client');?\s*\n/.exec(source);
+    if (directive) {
+        const end = directive.index + directive[0].length;
+        return `${source.slice(0, end)}\n${importLine}${source.slice(end)}`;
+    }
+    return `${importLine}\n${source}`;
+}
+/**
+ * Put `markup` immediately inside the closing `</body>`.
+ *
+ * Shared by both strategies because the placement problem is the same one in
+ * JSX and in HTML, and the interesting case is the same too: the one-line
+ * `<body>…</body>` that Next's template and hand-written HTML pages both use.
+ */
+function insertBeforeClosingBody(source, markup) {
+    const closingBody = source.lastIndexOf("</body>");
+    if (closingBody === -1) {
+        // Refusing beats guessing. A layout with no <body> is not an App Router
+        // root layout, and injecting somewhere plausible would produce a build
+        // failure the developer has to reverse-engineer.
+        throw new InjectionError("found a layout file but no <body> tag to place the toolbar in");
+    }
+    // Immediately before `</body>`, never at the start of its line: Next's own
+    // template ships `<body>{children}</body>` on one line, and inserting at the
+    // line start would put the toolbar between <html> and <body>, which is a
+    // broken layout rather than an install.
+    const lineStart = source.lastIndexOf("\n", closingBody) + 1;
+    const beforeOnLine = source.slice(lineStart, closingBody);
+    const openingBodyOnSameLine = beforeOnLine.includes("<body");
+    if (openingBodyOnSameLine) {
+        // Everything is on one line, so splice in place rather than reformat.
+        return `${source.slice(0, closingBody)}${markup}${source.slice(closingBody)}`;
+    }
+    // `</body>` is on its own line: take its indentation plus one step, so the
+    // diff reads as if a person wrote it.
+    const indent = beforeOnLine.match(/^\s*/)?.[0] ?? "";
+    const line = `${indent}  ${markup}\n`;
+    return `${source.slice(0, lineStart)}${line}${source.slice(lineStart)}`;
+}
+/** A failure the developer can act on, as opposed to an internal error. */
+export class InjectionError extends Error {
+    constructor(message) {
+        super(message);
+        this.name = "InjectionError";
+    }
+}
+export const STRATEGIES = [
+    nextAppRouterStrategy,
+    htmlScriptTagStrategy,
+];
+//# sourceMappingURL=strategies.js.map

package/dist/install/strategies.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"strategies.js","sourceRoot":"","sources":["../../src/install/strategies.ts"],"names":[],"mappings":"AAAA,wEAAwE;AACxE,EAAE;AACF,0EAA0E;AAC1E,+EAA+E;AAC/E,6EAA6E;AAC7E,mEAAmE;AAEnE,OAAO,EAAE,QAAQ,EAAoB,MAAM,MAAM,CAAC;AAElD;;;;;;;;;GASG;AACH,MAAM,CAAC,MAAM,YAAY,GAAG,0BAA0B,CAAC;AACvD,MAAM,CAAC,MAAM,cAAc,GAAG,iBAAiB,CAAC;AAEhD,+EAA+E;AAC/E,MAAM,CAAC,MAAM,kBAAkB,GAAG,aAAa,CAAC;AAwBhD;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,CAAC,MAAM,0BAA0B,GAAG,SAAS,CAAC;AAmCpD,sEAAsE;AACtE,MAAM,kBAAkB,GAAG;IACzB,gBAAgB;IAChB,oBAAoB;IACpB,gBAAgB;IAChB,oBAAoB;CACrB,CAAC;AAEF,MAAM,CAAC,MAAM,qBAAqB,GAAsB;IACtD,EAAE,EAAE,iBAAiB;IACrB,KAAK,EAAE,oBAAoB;IAC3B,QAAQ,EAAE,aAAa;IAEvB,MAAM,CAAC,EAAE,EAAE,IAAI;QACb,KAAK,MAAM,SAAS,IAAI,kBAAkB,EAAE,CAAC;YAC3C,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,EAAE,SAAS,CAAC,CAAC;YACvC,IAAI,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC;gBACpB,OAAO,EAAE,IAAI,EAAE,WAAW,EAAE,kBAAkB,SAAS,EAAE,EAAE,CAAC;YAC9D,CAAC;QACH,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IAED,WAAW,CAAC,MAAM;QAChB,0EAA0E;QAC1E,mEAAmE;QACnE,OAAO,CACL,MAAM,CAAC,QAAQ,CAAC,YAAY,CAAC,IAAI,MAAM,CAAC,QAAQ,CAAC,IAAI,cAAc,EAAE,CAAC,CACvE,CAAC;IACJ,CAAC;IAED,MAAM,CAAC,MAAM,EAAE,OAAO;QACpB,IAAI,GAAG,GAAG,MAAM,CAAC;QAEjB,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,YAAY,CAAC,EAAE,CAAC;YAChC,GAAG,GAAG,SAAS,CAAC,GAAG,CAAC,CAAC;QACvB,CAAC;QAED,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,cAAc,EAAE,CAAC,EAAE,CAAC;YACxC,yEAAyE;YACzE,sEAAsE;YACtE,8BAA8B;YAC9B,EAAE;YACF,0EAA0E;YAC1E,sEAAsE;YACtE,uEAAuE;YACvE,0EAA0E;YAC1E,wEAAwE;YACxE,kCAAkC;YAClC,EAAE;YACF,kEAAkE;YAClE,kEAAkE;YAClE,uEAAuE;YACvE,uEAAuE;YACvE,sEAAsE;YACtE,kDAAkD;YAClD,GAAG,GAAG,uBAAuB,CAC3B,GAAG,EACH,IAAI,cAAc,YAAY,OAAO,CAAC,MAAM,MAAM,CACnD,CAAC;QACJ,CAAC;QAED,OAAO,GAAG,CAAC;IACb,CAAC;CACF,CAAC;AAEF,qEAAqE;AACrE,MAAM,gBAAgB,GAAG,CAAC,YAAY,EAAE,mBAAmB,EAAE,gBAAgB,CAAC,CAAC;AAE/E;;;;;;;;;;;;;;;;GAgBG;AACH,MAAM,CAAC,MAAM,qBAAqB,GAAsB;IACtD,EAAE,EAAE,iBAAiB;IACrB,KAAK,EAAE,iBAAiB;IACxB,QAAQ,EAAE,YAAY;IAEtB,MAAM,CAAC,EAAE,EAAE,IAAI;QACb,KAAK,MAAM,SAAS,IAAI,gBAAgB,EAAE,CAAC;YACzC,MAAM,IAAI,GAAG,QAAQ,CAAC,IAAI,EAAE,SAAS,CAAC,CAAC;YACvC,IAAI,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC;gBACpB,OAAO,EAAE,IAAI,EAAE,WAAW,EAAE,gBAAgB,SAAS,EAAE,EAAE,CAAC;YAC5D,CAAC;QACH,CAAC;QACD,OAAO,IAAI,CAAC;IACd,CAAC;IAED,WAAW,CAAC,MAAM;QAChB,OAAO,MAAM,CAAC,QAAQ,CAAC,kBAAkB,CAAC,CAAC;IAC7C,CAAC;IAED,MAAM,CAAC,MAAM,EAAE,OAAO;QACpB,IAAI,CAAC,OAAO,CAAC,UAAU,EAAE,CAAC;YACxB,qEAAqE;YACrE,qEAAqE;YACrE,wEAAwE;YACxE,mEAAmE;YACnE,MAAM,IAAI,cAAc,CACtB,+EAA+E;gBAC7E,8CAA8C,CACjD,CAAC;QACJ,CAAC;QACD,MAAM,WAAW,GAAG,OAAO,CAAC,WAAW,IAAI,0BAA0B,CAAC;QACtE,OAAO,uBAAuB,CAC5B,MAAM,EACN,gBAAgB,OAAO,CAAC,MAAM,GAAG,kBAAkB,IAAI;YACrD,iBAAiB,OAAO,CAAC,MAAM,IAAI;YACnC,qBAAqB,OAAO,CAAC,UAAU,IAAI;YAC3C,qBAAqB,WAAW,mBAAmB,CACtD,CAAC;IACJ,CAAC;CACF,CAAC;AAEF,SAAS,SAAS,CAAC,MAAc;IAC/B,MAAM,UAAU,GAAG,YAAY,cAAc,YAAY,YAAY,MAAM,CAAC;IAE5E,sEAAsE;IACtE,+DAA+D;IAC/D,MAAM,QAAQ,GAAG,2BAA2B,CAAC;IAC7C,IAAI,OAAO,GAAG,CAAC,CAAC,CAAC;IACjB,KAAK,MAAM,KAAK,IAAI,MAAM,CAAC,QAAQ,CAAC,QAAQ,CAAC,EAAE,CAAC;QAC9C,OAAO,GAAG,KAAK,CAAC,KAAK,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC;IAC1C,CAAC;IACD,IAAI,OAAO,IAAI,CAAC,EAAE,CAAC;QACjB,OAAO,GAAG,MAAM,CAAC,KAAK,CAAC,CAAC,EAAE,OAAO,CAAC,KAAK,UAAU,CAAC,OAAO,EAAE,GAAG,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,EAAE,CAAC;IACxF,CAAC;IAED,2EAA2E;IAC3E,iCAAiC;IACjC,MAAM,SAAS,GAAG,wCAAwC,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;IACxE,IAAI,SAAS,EAAE,CAAC;QACd,MAAM,GAAG,GAAG,SAAS,CAAC,KAAK,GAAG,SAAS,CAAC,CAAC,CAAC,CAAC,MAAM,CAAC;QAClD,OAAO,GAAG,MAAM,CAAC,KAAK,CAAC,CAAC,EAAE,GAAG,CAAC,KAAK,UAAU,GAAG,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,EAAE,CAAC;IACtE,CAAC;IACD,OAAO,GAAG,UAAU,KAAK,MAAM,EAAE,CAAC;AACpC,CAAC;AAED;;;;;;GAMG;AACH,SAAS,uBAAuB,CAAC,MAAc,EAAE,MAAc;IAC7D,MAAM,WAAW,GAAG,MAAM,CAAC,WAAW,CAAC,SAAS,CAAC,CAAC;IAClD,IAAI,WAAW,KAAK,CAAC,CAAC,EAAE,CAAC;QACvB,wEAAwE;QACxE,uEAAuE;QACvE,iDAAiD;QACjD,MAAM,IAAI,cAAc,CACtB,+DAA+D,CAChE,CAAC;IACJ,CAAC;IAED,2EAA2E;IAC3E,6EAA6E;IAC7E,yEAAyE;IACzE,wCAAwC;IACxC,MAAM,SAAS,GAAG,MAAM,CAAC,WAAW,CAAC,IAAI,EAAE,WAAW,CAAC,GAAG,CAAC,CAAC;IAC5D,MAAM,YAAY,GAAG,MAAM,CAAC,KAAK,CAAC,SAAS,EAAE,WAAW,CAAC,CAAC;IAC1D,MAAM,qBAAqB,GAAG,YAAY,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;IAE7D,IAAI,qBAAqB,EAAE,CAAC;QAC1B,sEAAsE;QACtE,OAAO,GAAG,MAAM,CAAC,KAAK,CAAC,CAAC,EAAE,WAAW,CAAC,GAAG,MAAM,GAAG,MAAM,CAAC,KAAK,CAAC,WAAW,CAAC,EAAE,CAAC;IAChF,CAAC;IAED,2EAA2E;IAC3E,sCAAsC;IACtC,MAAM,MAAM,GAAG,YAAY,CAAC,KAAK,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IACrD,MAAM,IAAI,GAAG,GAAG,MAAM,KAAK,MAAM,IAAI,CAAC;IACtC,OAAO,GAAG,MAAM,CAAC,KAAK,CAAC,CAAC,EAAE,SAAS,CAAC,GAAG,IAAI,GAAG,MAAM,CAAC,KAAK,CAAC,SAAS,CAAC,EAAE,CAAC;AAC1E,CAAC;AAED,2EAA2E;AAC3E,MAAM,OAAO,cAAe,SAAQ,KAAK;IACvC,YAAY,OAAe;QACzB,KAAK,CAAC,OAAO,CAAC,CAAC;QACf,IAAI,CAAC,IAAI,GAAG,gBAAgB,CAAC;IAC/B,CAAC;CACF;AAED,MAAM,CAAC,MAAM,UAAU,GAAiC;IACtD,qBAAqB;IACrB,qBAAqB;CACtB,CAAC"}

package/dist/registration.d.ts

@@ -0,0 +1,43 @@
+/** What a build environment can tell the backend about the deployment. */
+export interface RegisterProjectRequest {
+    /** Base URL of the BitVea Feedback backend. */
+    apiUrl: string;
+    /** Deploy key. Read from a flag or the environment, never from a file. */
+    apiKey: string;
+    /** The deployment URL to register, exactly as the caller resolved it. */
+    projectUrl: string;
+    repoOwner?: string | undefined;
+    repoSlug?: string | undefined;
+    packageName?: string | undefined;
+    /**
+     * Browser origins this deployment serves the toolbar from, which is not the
+     * same question as `projectUrl` and is why both are sent. See
+     * `inferProjectOrigins`.
+     */
+    origins?: string[] | undefined;
+}
+/**
+ * `created` is the whole answer: false means the URL was already registered,
+ * which is a success, not a conflict. `project` is what the backend named it,
+ * so the CLI can echo something recognisable back.
+ */
+export interface RegisterProjectResponse {
+    created: boolean;
+    project?: {
+        id: string;
+        name: string;
+        slug: string;
+        url: string | null;
+    };
+}
+export type RegisterProjectTransport = (input: RegisterProjectRequest) => Promise<RegisterProjectResponse>;
+/**
+ * A failure the person running the command can act on, as opposed to a bug.
+ * The CLI prints `message` and exits; nothing else is expected to catch it.
+ */
+export declare class RegistrationError extends Error {
+    constructor(message: string);
+}
+/** The real transport. Injected everywhere else so tests stay off the network. */
+export declare const postRegistration: RegisterProjectTransport;
+//# sourceMappingURL=registration.d.ts.map

package/dist/registration.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"registration.d.ts","sourceRoot":"","sources":["../src/registration.ts"],"names":[],"mappings":"AAcA,0EAA0E;AAC1E,MAAM,WAAW,sBAAsB;IACrC,+CAA+C;IAC/C,MAAM,EAAE,MAAM,CAAC;IACf,0EAA0E;IAC1E,MAAM,EAAE,MAAM,CAAC;IACf,yEAAyE;IACzE,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC/B,QAAQ,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IAC9B,WAAW,CAAC,EAAE,MAAM,GAAG,SAAS,CAAC;IACjC;;;;OAIG;IACH,OAAO,CAAC,EAAE,MAAM,EAAE,GAAG,SAAS,CAAC;CAChC;AAED;;;;GAIG;AACH,MAAM,WAAW,uBAAuB;IACtC,OAAO,EAAE,OAAO,CAAC;IACjB,OAAO,CAAC,EAAE;QAAE,EAAE,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAC;QAAC,IAAI,EAAE,MAAM,CAAC;QAAC,GAAG,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAAC;CAC1E;AAED,MAAM,MAAM,wBAAwB,GAAG,CACrC,KAAK,EAAE,sBAAsB,KAC1B,OAAO,CAAC,uBAAuB,CAAC,CAAC;AAEtC;;;GAGG;AACH,qBAAa,iBAAkB,SAAQ,KAAK;gBAC9B,OAAO,EAAE,MAAM;CAI5B;AAED,kFAAkF;AAClF,eAAO,MAAM,gBAAgB,EAAE,wBAwE9B,CAAC"}