@mittwald/flow-codemods 1.2.0-next.5 → 1.2.0-next.51

package/dist/install.js

@@ -1,38 +1,45 @@
 import { execFileSync } from "node:child_process";
-import { existsSync } from "node:fs";
-import { join } from "node:path";
-/** Lockfile to manager, in precedence order. */
-const lockfiles = [
-    ["pnpm-lock.yaml", "pnpm"],
-    // Both Bun lockfile names: `bun.lock` (text) is the default only from Bun
-    // 1.2; before that Bun writes the binary `bun.lockb`, which plenty of
-    // projects still have. Missing it would fall through to the npm default and
-    // run `npm install` on a Bun project, leaving a stray package-lock.json.
-    ["bun.lock", "bun"],
-    ["bun.lockb", "bun"],
-    ["yarn.lock", "yarn"],
-    ["package-lock.json", "npm"],
+import { satisfies, validRange } from "semver";
+import { resolveCommand } from "package-manager-detector/commands";
+import { INSTALL_PAGE } from "package-manager-detector/constants";
+import { detect } from "package-manager-detector/detect";
+/** Every strategy the library offers, in the order it applies them. */
+const strategies = [
+    "lockfile",
+    "packageManager-field",
+    "devEngines-field",
+    // Not in the library's default set. `upgrade` always runs on an installed
+    // project — it reads `node_modules` to learn the current Flow version — so the
+    // marker a manager leaves in there is a real signal, and the last one before
+    // the npm fallback.
+    "install-metadata",
 ];
+/** What a project with no signal at all gets. */
+const fallback = { name: "npm", agent: "npm" };
 /**
- * The package manager a project uses, from the lockfiles present.
+ * The package manager for the project at `cwd`.
  *
- * Npm is the fallback: it is the one manager that is always available next to
- * Node, so a project with no lockfile still gets an install rather than an
- * error.
+ * Detection walks **up** from `cwd`, which is the whole point: the previous
+ * implementation looked for lockfiles in `cwd` only, and a workspace package
+ * has none of its own. In a Yarn or pnpm monorepo it therefore fell through to
+ * the npm default and ran `npm install`, which on a workspace manifest dies
+ * with `EUNSUPPORTEDPROTOCOL Unsupported URL Type "workspace:"` — after
+ * `upgrade` had already rewritten `package.json`. It also ignored
+ * `packageManager` entirely.
+ *
+ * Per directory the strategies are applied in order, so a lockfile in `cwd`
+ * still beats a `packageManager` pin in a parent — and when the lockfile
+ * strategy hits, the library reads that same directory's `package.json` and
+ * lets its pin win. That is the precedence we want, and it is the library's,
+ * not ours.
+ *
+ * Npm on `null`, preserving the old fallback: it is the one manager always
+ * present next to Node, so a project with no signal gets an install rather than
+ * an error.
  */
-export const detectPackageManager = (present) => {
-    for (const [lockfile, manager] of lockfiles) {
-        if (present.includes(lockfile)) {
-            return manager;
-        }
-    }
-    return "npm";
-};
-export const detectPackageManagerIn = (cwd) => detectPackageManager(lockfiles
-    .map(([lockfile]) => lockfile)
-    .filter((lockfile) => existsSync(join(cwd, lockfile))));
+export const detectPackageManagerIn = async (cwd) => (await detect({ cwd, strategies: [...strategies] })) ?? fallback;
 /**
- * How to install with a given manager, so that the install actually updates the
+ * How to install with `agent`, so that the install actually updates the
  * lockfile.
  *
  * `upgrade` has just rewritten `package.json`, so the lockfile is deliberately
@@ -40,32 +47,138 @@ export const detectPackageManagerIn = (cwd) => detectPackageManager(lockfiles
  * themselves when they detect CI, where an install then _fails_ instead of
  * updating — and CI is exactly where this runs unattended. pnpm takes a flag;
  * Yarn's flag differs between Classic and Berry, so it gets the environment
- * variable instead, which Classic ignores harmlessly.
+ * variable instead, which Classic ignores harmlessly. Keeping the env var also
+ * keeps this one code path rather than branching on a Berry detection being
+ * right.
+ *
+ * The command itself comes from the library. Its `"install"` is the plain
+ * install for every agent — the frozen variants are a separate command there —
+ * so these quirks stay ours.
+ */
+export const installCommand = (agent) => {
+    const frozenOptOut = agent.startsWith("pnpm") ? ["--no-frozen-lockfile"] : [];
+    const resolved = resolveCommand(agent, "install", frozenOptOut);
+    if (resolved === null) {
+        throw new Error(`${agent} has no install command. Install the dependencies yourself, then re-run this command.`);
+    }
+    return {
+        command: resolved.command,
+        args: resolved.args,
+        env: agent.startsWith("yarn")
+            ? { YARN_ENABLE_IMMUTABLE_INSTALLS: "false" }
+            : {},
+    };
+};
+/**
+ * The pin as a semver range, or `undefined` when there is nothing to check.
+ *
+ * Two values have to be filtered out. `"berry"` is what the library reports for
+ * Yarn 2+ — a specifier, not a version — and for an unparseable
+ * `packageManager` it hands back the raw string. Neither is a range, and
+ * `satisfies` would throw on both.
+ *
+ * A full pin like `8.15.0` is a valid range meaning exactly that version, so
+ * one comparison covers both `pnpm@8` and `pnpm@8.15.0`. That is also why this
+ * is `satisfies` and not a string compare: the library reports the
+ * `\d+(\.\d+){0,2}` match out of the field, so `packageManager: "pnpm@8"`
+ * yields the pin `"8"` while the binary reports `8.15.0` — a string compare
+ * would send a perfectly fine setup through corepack.
  */
-export const installCommand = (manager) => {
-    switch (manager) {
-        case "pnpm":
-            return {
-                command: "pnpm",
-                args: ["install", "--no-frozen-lockfile"],
-                env: {},
-            };
-        case "yarn":
-            return {
-                command: "yarn",
-                args: ["install"],
-                env: { YARN_ENABLE_IMMUTABLE_INSTALLS: "false" },
-            };
-        case "npm":
-        case "bun":
-            return { command: manager, args: ["install"], env: {} };
+export const pinnedRange = (version) => version !== undefined && version !== "berry" && validRange(version) !== null
+    ? version
+    : undefined;
+export const runProbe = (command, args) => {
+    try {
+        return execFileSync(command, args, {
+            encoding: "utf8",
+            stdio: ["ignore", "pipe", "ignore"],
+            shell: process.platform === "win32",
+        }).trim();
+    }
+    catch {
+        return undefined;
     }
 };
+/**
+ * What to run for `manager`, honouring a `packageManager` pin.
+ *
+ * The decision tree, and why it checks before reaching for corepack:
+ *
+ * | Situation                                         | Behaviour                 |
+ * | ------------------------------------------------- | ------------------------- |
+ * | No pin, or the `"berry"` specifier                | run directly              |
+ * | Pin, binary present, version satisfies it         | run directly              |
+ * | Pin, mismatch or binary missing, corepack present | run under corepack        |
+ * | Pin, mismatch or missing, no corepack             | throw, before any install |
+ *
+ * Corepack ignores `PATH` and downloads into its own cache, so "always
+ * corepack" would send every project that has a `packageManager` field — most
+ * of them — through a download, offline CI included. pnpm 9.7+ additionally
+ * installs its own pinned version, so for pnpm the direct path is usually
+ * already right.
+ *
+ * `COREPACK_ENABLE_DOWNLOAD_PROMPT=0` is required rather than tidy: corepack
+ * prompts interactively before a first download, and `upgrade` runs unattended
+ * (`-y` is implied with no TTY). Only one `install` is spawned under corepack —
+ * no nested per-task spawns — so the corepack footgun in the repo's root
+ * `AGENTS.md` does not apply.
+ */
+export const planInstall = (manager, probe = runProbe) => {
+    const { command, args, env } = installCommand(manager.agent);
+    const line = [command, ...args].join(" ");
+    const pin = pinnedRange(manager.version);
+    if (pin === undefined) {
+        return { command, args, env, description: `${manager.agent} — ${line}` };
+    }
+    const found = probe(command, ["--version"]);
+    if (found !== undefined && satisfies(found, pin)) {
+        return {
+            command,
+            args,
+            env,
+            description: `${manager.agent} ${found} — ${line}`,
+        };
+    }
+    if (probe("corepack", ["--version"]) === undefined) {
+        throw new Error(`This project pins ${manager.name}@${pin} in "packageManager", but ${found === undefined
+            ? `${command} is not on PATH`
+            : `the ${command} on PATH is ${found}`}, and corepack is not available to bridge the gap.\n\nInstall ${manager.name}@${pin} (${INSTALL_PAGE[manager.agent]}) or enable corepack, then re-run this command. Nothing has been installed.`);
+    }
+    return {
+        command: "corepack",
+        args: [command, ...args],
+        env: { ...env, COREPACK_ENABLE_DOWNLOAD_PROMPT: "0" },
+        description: `${manager.agent} ${pin} via corepack — corepack ${line}`,
+    };
+};
 export const runInstall = (manager, cwd) => {
-    const { command, args, env } = installCommand(manager);
-    execFileSync(command, args, {
+    const plan = planInstall(manager);
+    execFileSync(plan.command, plan.args, {
         cwd,
         stdio: "inherit",
-        env: { ...process.env, ...env },
+        env: { ...process.env, ...plan.env },
+        // Node has refused to spawn `.cmd`/`.bat` without a shell since 2024, which
+        // is why every non-npm manager died with ENOENT on Windows. Every argument
+        // here is our own literal or the library's, so there is no quoting hazard.
+        shell: process.platform === "win32",
     });
+    return plan.description;
+};
+/**
+ * How to tell a reader to invoke this package, for the manager they use.
+ *
+ * `npx …` for npm and Yarn Classic (which has no `dlx`), `pnpm dlx …`, `yarn
+ * dlx …`, `bun x …`. The package name is passed as an argument rather than
+ * baked in, so the library decides the whole prefix.
+ *
+ * Falls back to the `npx` form when the agent has no `execute` command: a
+ * printed hint is worth more than a gap, and npx is the one form every reader
+ * can run.
+ */
+export const resolveInvoke = async (cwd, pkg = "@mittwald/flow-codemods@latest") => {
+    const { agent } = await detectPackageManagerIn(cwd);
+    const resolved = resolveCommand(agent, "execute", [pkg]);
+    return resolved === null
+        ? `npx ${pkg}`
+        : [resolved.command, ...resolved.args].join(" ");
 };

package/dist/manifest.d.ts

@@ -42,4 +42,3 @@ export declare const applyTarget: <T extends Manifest>(manifest: T, target: stri
  * `imports-to-package-root` needed an explicit leave-alone set to earn this.
  */
 export declare const detectCurrentVersion: (dependencies: FlowDependency[], readInstalledVersion: (name: string) => string | undefined) => string | undefined;
-//# sourceMappingURL=manifest.d.ts.map

package/dist/migrations/action-prop-to-on-action/transform.js

@@ -1,7 +1,8 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 /**
- * Renames the `action` prop to `onAction` on `Action`.
+ * Renames the `action` prop to `onAction` on `Action`, and wraps a bare
+ * function reference passed to it in an inline call.
  *
  * The scope is deliberately narrow. Only JSX elements that resolve to `Action`
  * — imported (named or as a namespace) from `@mittwald/flow-react-components`
@@ -14,6 +15,44 @@ Object.defineProperty(exports, "__esModule", { value: true });
  * An element that already carries `onAction` keeps it and only loses the stale
  * `action` prop, which mirrors what the runtime fallback does: an explicit
  * `onAction` wins.
+ *
+ * ## Why the wrap is unconditional
+ *
+ * `onAction` is typed `ActionFn` (`(...args: unknown[]) => unknown`), so a
+ * reference to a function declaring a parameter of any narrower type — the
+ * usual case being `controller.close`, typed `(options?: CloseOverlayOptions)
+ * => void` — does not type-check. Whether a given reference declares such a
+ * parameter needs type information and is not decidable from the source, which
+ * is why this transform used to leave every reference alone and `apply` asked
+ * for a manual pass over all of them.
+ *
+ * Deciding _whether_ to wrap needs the type. _Performing_ the wrap does not:
+ * `() => fn()` calls exactly what `fn` would have been called with by `Action`,
+ * minus the arguments — and `onAction` is documented as taking none. So the
+ * wrap fixes the reference that needed it and is a no-op for the rest, which
+ * makes the decision unnecessary.
+ *
+ * Two cases it can still change, neither decidable from the source:
+ *
+ * - A handler that reads the argument `Action` forwards (the trigger's event,
+ *   e.g. a `PressEvent` from the `Button` inside) and declares it optional or
+ *   as a rest parameter, so that it type-checks both before and after. It stops
+ *   receiving that argument, silently. Nothing in Flow documents `onAction` as
+ *   receiving one.
+ * - A possibly-undefined reference, `onAction={props.onAction}`. `undefined` is a
+ *   valid value for the prop, but calling it is not, so the wrap turns
+ *   something TypeScript accepted into something it rejects — loudly, at the
+ *   call site, which is why this is a compile error to fix rather than a
+ *   regression to find.
+ *
+ * `apply` names both.
+ *
+ * Only a bare reference is wrapped: a plain identifier or a member expression.
+ * An arrow function and a function expression already are the handler. A call
+ * (`makeHandler()`, `close.bind(controller)`) _produces_ the handler, so
+ * wrapping it would call the factory on every trigger and throw its result
+ * away. A conditional, a `??` chain or an optional member expression is not a
+ * reference to one function, so wrapping would be a guess.
  */
 const actionPropToOnActionTransform = (fileInfo, { j }) => {
     const flowPackages = [
@@ -22,6 +61,27 @@ const actionPropToOnActionTransform = (fileInfo, { j }) => {
     ];
     const affectedComponents = new Set(["Action"]);
     const isFlowImport = (source) => flowPackages.some((pkg) => source === pkg || source.startsWith(`${pkg}/`));
+    /**
+     * Whether a member expression is rooted in a plain reference —
+     * `controller.close`, `this.handleSave`, `store.modal.controller.close` —
+     * rather than in something evaluated, as `makeController().close` is.
+     *
+     * An optional link disqualifies the chain. `controller?.close` parses as
+     * `OptionalMemberExpression` and never reaches here at all; walking the chain
+     * catches a mixed one like `(a?.b).c`. Declining is deliberate: `() =>
+     * controller?.close()` short-circuits differently from the value it would
+     * replace, and the spelling says the reference may not be there.
+     */
+    const hasPlainObjectChain = (expression) => {
+        const object = expression.object;
+        if (!object || typeof object !== "object" || !("type" in object)) {
+            return false;
+        }
+        const typed = object;
+        return (typed.type === "ThisExpression" ||
+            typed.type === "Identifier" ||
+            (typed.type === "MemberExpression" && hasPlainObjectChain(typed)));
+    };
     const root = j(fileInfo.source, { parser: "tsx" });
     // Local JSX identifier -> canonical component name (resolves `as` aliases).
     const localToComponent = new Map();
@@ -69,12 +129,38 @@ const actionPropToOnActionTransform = (fileInfo, { j }) => {
         const hasOnAction = attributes.some((attribute) => isNamed(attribute, "onAction"));
         if (hasOnAction) {
             path.node.attributes = attributes.filter((attribute) => !isNamed(attribute, "action"));
-            return;
         }
-        for (const attribute of attributes) {
-            if (isNamed(attribute, "action") && attribute.type === "JSXAttribute") {
-                attribute.name.name = "onAction";
+        else {
+            for (const attribute of attributes) {
+                if (isNamed(attribute, "action") && attribute.type === "JSXAttribute") {
+                    attribute.name.name = "onAction";
+                }
+            }
+        }
+        // Whatever the prop was called before, the surviving `onAction` is the one
+        // that needs the wrap — including one the consumer had already renamed by
+        // hand, which carries the same type error.
+        for (const attribute of path.node.attributes ?? []) {
+            if (attribute.type !== "JSXAttribute" ||
+                !isNamed(attribute, "onAction")) {
+                continue;
+            }
+            const container = attribute.value;
+            if (container?.type !== "JSXExpressionContainer") {
+                continue;
+            }
+            // A bare reference is an identifier or a member expression. Everything
+            // else either is the handler already or is a way of producing one.
+            const expression = container.expression;
+            if (expression.type !== "Identifier" &&
+                expression.type !== "MemberExpression") {
+                continue;
+            }
+            if (expression.type === "MemberExpression" &&
+                !hasPlainObjectChain(expression)) {
+                continue;
             }
+            attribute.value = j.jsxExpressionContainer(j.arrowFunctionExpression([], j.callExpression(expression, [])));
         }
     });
     return root.toSource();

package/dist/migrations/renamed-css-export/transform.js

@@ -0,0 +1,59 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+const oldPath = "@mittwald/flow-react-components/styles";
+const newPath = "@mittwald/flow-react-components/all.css";
+/**
+ * Rewrites the module specifier `@mittwald/flow-react-components/styles` to
+ * `@mittwald/flow-react-components/all.css` (alpha.292).
+ *
+ * The same shape as `password-tools-subpath-renamed`: one exact specifier, in
+ * every form that names a module — `import`, `import type`, `export … from`, a
+ * side-effect import, `import()` and `require()`. In practice it is nearly
+ * always the side-effect form (`import "…/styles"`), which is why that case is
+ * the one the fixtures lead with.
+ *
+ * Exact match, not a prefix: `./styles` was a single export with nothing
+ * underneath it, so there is no deeper path to rewrite and no risk of touching
+ * an unrelated `styles` of someone else's.
+ *
+ * What this cannot reach is an `@import` in a `.css` or `.scss` file —
+ * jscodeshift only walks the JavaScript and TypeScript extensions. `apply` says
+ * so.
+ */
+const renamedCssExportTransform = (fileInfo, { j }) => {
+    const root = j(fileInfo.source, { parser: "tsx" });
+    let changed = false;
+    const rewrite = (node) => {
+        if (node.value === oldPath) {
+            node.value = newPath;
+            changed = true;
+        }
+    };
+    // import … from "…", import "…"
+    root.find(j.ImportDeclaration).forEach((path) => rewrite(path.node.source));
+    // export … from "…", export * from "…"
+    root
+        .find(j.ExportNamedDeclaration)
+        .forEach((path) => path.node.source && rewrite(path.node.source));
+    root
+        .find(j.ExportAllDeclaration)
+        .forEach((path) => rewrite(path.node.source));
+    // import("…") and require("…")
+    root
+        .find(j.CallExpression)
+        .filter((path) => {
+        const callee = path.node.callee;
+        return (callee.type === "Import" ||
+            (callee.type === "Identifier" && callee.name === "require"));
+    })
+        .forEach((path) => {
+        const [argument] = path.node.arguments;
+        if (argument &&
+            (argument.type === "StringLiteral" || argument.type === "Literal")) {
+            rewrite(argument);
+        }
+    });
+    // Returning the source untouched keeps this file out of the "changed" count.
+    return changed ? root.toSource() : fileInfo.source;
+};
+exports.default = renamedCssExportTransform;

package/dist/migrations/table-column-width-props/transform.js

@@ -0,0 +1,131 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+/**
+ * Drops `maxWidth` from `TableColumn`, and drops `width`/`minWidth` where they
+ * were `null` (alpha.956).
+ *
+ * Two changes with different decidability, which is why the transform covers
+ * both but not equally:
+ *
+ * - **`maxWidth` always goes.** The prop was removed from the type, so an
+ *   explicit `maxWidth` attribute is wrong whatever its value is —
+ *   `maxWidth={400}` and `maxWidth={computed}` alike. Removing it does change
+ *   the rendered column (there is no maximum any more); that is the migration,
+ *   not a side effect.
+ * - **`width` and `minWidth` only go when the source says `null`.** The type
+ *   dropped `null`, and `null` meant "no explicit width", which is what
+ *   omitting the prop means now. Only the literal is decidable:
+ *   `width={maybeNull}` could be anything at runtime and is left alone, the way
+ *   `accent-box-color-to-background-color` leaves `color={expression}`.
+ *
+ * The scope is the same as its neighbours': only JSX elements that resolve to
+ * `TableColumn` — imported named, aliased, or through a namespace, from
+ * `@mittwald/flow-react-components` or
+ * `@mittwald/flow-remote-react-components`, including their subpath entries.
+ *
+ * A spread (`<TableColumn {...props} />`) carrying `maxWidth` is invisible
+ * here. The explicit attributes beside it are still handled; `apply` names the
+ * gap.
+ */
+const tableColumnWidthPropsTransform = (fileInfo, { j }) => {
+    const flowPackages = [
+        "@mittwald/flow-react-components",
+        "@mittwald/flow-remote-react-components",
+    ];
+    const affectedComponents = new Set(["TableColumn"]);
+    /** Removed from the type — an explicit attribute is wrong at any value. */
+    const removedProps = new Set(["maxWidth"]);
+    /** Retyped without `null` — remove only where the source literally says so. */
+    const nullableProps = new Set(["width", "minWidth"]);
+    const isFlowImport = (source) => flowPackages.some((pkg) => source === pkg || source.startsWith(`${pkg}/`));
+    /**
+     * Whether this JSX attribute value is the literal `null`.
+     *
+     * Both spellings, because which one appears depends on the parser: babel
+     * emits `NullLiteral`, esprima-style parsers a `Literal` whose `value` is
+     * `null`. Anything else — an identifier, a call, a ternary — is not decidable
+     * from the source and stays.
+     */
+    const isNullLiteral = (value) => {
+        if (!value || typeof value !== "object" || !("type" in value)) {
+            return false;
+        }
+        const container = value;
+        if (container.type !== "JSXExpressionContainer") {
+            return false;
+        }
+        const expression = container.expression;
+        if (!expression ||
+            typeof expression !== "object" ||
+            !("type" in expression)) {
+            return false;
+        }
+        const typed = expression;
+        return (typed.type === "NullLiteral" ||
+            (typed.type === "Literal" && typed.value === null));
+    };
+    const root = j(fileInfo.source, { parser: "tsx" });
+    // Local JSX identifier -> canonical component name (resolves `as` aliases).
+    const localToComponent = new Map();
+    // Local names of `import * as Flow` namespace imports from a Flow package.
+    const flowNamespaces = new Set();
+    root
+        .find(j.ImportDeclaration)
+        .filter((path) => isFlowImport(String(path.node.source.value)))
+        .forEach((path) => {
+        for (const specifier of path.node.specifiers ?? []) {
+            if (specifier.type === "ImportSpecifier" &&
+                specifier.imported.type === "Identifier" &&
+                affectedComponents.has(specifier.imported.name)) {
+                localToComponent.set(String(specifier.local?.name ?? specifier.imported.name), String(specifier.imported.name));
+            }
+            else if (specifier.type === "ImportNamespaceSpecifier" &&
+                specifier.local) {
+                flowNamespaces.add(String(specifier.local.name));
+            }
+        }
+    });
+    if (localToComponent.size === 0 && flowNamespaces.size === 0) {
+        return fileInfo.source;
+    }
+    let changed = false;
+    root.find(j.JSXOpeningElement).forEach((path) => {
+        const name = path.node.name;
+        let isAffected = false;
+        if (name.type === "JSXIdentifier") {
+            isAffected = localToComponent.has(name.name);
+        }
+        else if (name.type === "JSXMemberExpression" &&
+            name.object.type === "JSXIdentifier" &&
+            name.property.type === "JSXIdentifier") {
+            isAffected =
+                flowNamespaces.has(name.object.name) &&
+                    affectedComponents.has(name.property.name);
+        }
+        if (!isAffected) {
+            return;
+        }
+        const attributes = path.node.attributes ?? [];
+        const kept = attributes.filter((attribute) => {
+            if (attribute.type !== "JSXAttribute" ||
+                attribute.name.type !== "JSXIdentifier") {
+                return true;
+            }
+            const attributeName = attribute.name.name;
+            if (removedProps.has(attributeName)) {
+                return false;
+            }
+            if (nullableProps.has(attributeName) && isNullLiteral(attribute.value)) {
+                return false;
+            }
+            return true;
+        });
+        if (kept.length !== attributes.length) {
+            path.node.attributes = kept;
+            changed = true;
+        }
+    });
+    // Returning the source untouched keeps this file out of the "changed" count.
+    return changed ? root.toSource() : fileInfo.source;
+};
+exports.default = tableColumnWidthPropsTransform;

package/dist/migrations.generated.d.ts

@@ -1,4 +1,3 @@
 import type { MigrationEntry } from "./catalog/types.js";
 /** Every migration, newest first. Bodies live in `src/migrations`. */
 export declare const migrations: Omit<MigrationEntry, "body">[];
-//# sourceMappingURL=migrations.generated.d.ts.map

package/dist/migrations.generated.js

@@ -3,6 +3,24 @@
 // Source: packages/codemods/src/migrations/<id>/entry.md
 /** Every migration, newest first. Bodies live in `src/migrations`. */
 export const migrations = [
+    {
+        id: "tabler-icons-no-longer-transitive",
+        since: "1.1.40",
+        title: "@tabler/icons-react is no longer installed alongside Flow",
+        kind: "migration",
+        action: "manual",
+        remotePackage: true,
+        apply: "Only affects code that imports from `@tabler/icons-react` — typically a `<Icon><IconSomething /></Icon>` using an icon that is not in Flow's own set. Add the package to your own dependencies (`npm i @tabler/icons-react`); the imports themselves stay unchanged. Flow's own `Icon*` components are unaffected, keep their names, and render exactly as before.",
+    },
+    {
+        id: "option-value-inferred-from-mixed-children",
+        since: "1.1.12",
+        title: "Option: value is inferred from mixed children",
+        kind: "migration",
+        action: "none",
+        remotePackage: true,
+        apply: "No code change required for the option itself. An `Option` whose children are text plus an element — text and a `Badge`, text and an icon — now carries that text as its key, where it previously fell back to react-aria's generated `react-aria-N`. Check anywhere such a key was read back: a stored or server-side selection, a `defaultValue`/`value` matched against it, or a test asserting on it. Pass an explicit `value` to pin the key to something other than the display text.",
+    },
     {
         id: "use-design-tokens-build-metadata-removed",
         since: "1.0.16",
@@ -75,14 +93,23 @@ export const migrations = [
         remotePackage: false,
         apply: "Replace the import path `@mittwald/flow-react-components/password-tools` with `@mittwald/flow-react-components/mittwald-password-tools-js`.",
     },
+    {
+        id: "tabs-navigation-usage-to-tab-navigation",
+        since: "0.2.0-alpha.977",
+        title: "Tabs restyled; navigation usage moves to TabNavigation",
+        kind: "migration",
+        action: "manual",
+        remotePackage: true,
+        apply: "Tabs' rendering changed: the tab list now fills the available width with equal-size tabs and a shared, animated indicator that slides between them, replacing the previous fit-content tabs that each carried their own hover/pressed/selected background. Nothing else about `Tabs` changed, and a `Tabs` that switches content within a page needs no code change — the new look applies on upgrade. Where `Tabs` was used to fake real navigation instead — a `TabTitle` given an `href` (`Aria.Tab`'s routing props: `href`, `target`, `routerOptions`, …) so selecting it pushed a real route change — replace it with `TabNavigation`: plain `Link` children instead of `Tab`/`TabTitle`/panels, `aria-current=\"page\"` on the active `Link` instead of `selectedKey`/`defaultSelectedKey`/`onSelectionChange`. `TabNavigation` keeps the visual language the old `Tabs` used to have, because it now owns that use case.",
+    },
     {
         id: "table-column-width-props",
         since: "0.2.0-alpha.956",
         title: "TableColumn: `maxWidth` removed, `width` and `minWidth` retyped",
         kind: "migration",
-        action: "manual",
+        action: "codemod",
         remotePackage: true,
-        apply: "Remove `maxWidth` from every `TableColumn`. Where `width` or `minWidth` was `null`, omit the prop instead — the type no longer accepts `null`, only `number | string`.",
+        apply: "Remove `maxWidth` from every `TableColumn`. Where `width` or `minWidth` was `null`, omit the prop instead — the type no longer accepts `null`, only `number | string`. A codemod does both for the cases it can decide from the source. Two it declines: a `width`/`minWidth` whose value is an expression (`width={maybeNull}`), and a spread that might carry `maxWidth` (`<TableColumn {...props} />`). Check those by hand.",
     },
     {
         id: "table-render-prop-removed",
@@ -190,7 +217,7 @@ export const migrations = [
         kind: "migration",
         action: "codemod",
         remotePackage: true,
-        apply: "Rename the `action` prop on `Action` to `onAction`. Not only a rename: the new prop is typed `ActionFn` (`(...args: unknown[]) => unknown`), so a function *reference* that declares a parameter no longer type-checks and needs wrapping — `onAction={() => controller.close()}` rather than `onAction={controller.close}`. Check every site where you passed a reference rather than an inline arrow; the codemod renames the prop but cannot decide this one from the source.",
+        apply: "Rename the `action` prop on `Action` to `onAction`. Not only a rename: the new prop is typed `ActionFn` (`(...args: unknown[]) => unknown`), so a function *reference* that declares a parameter no longer type-checks and needs wrapping — `onAction={() => controller.close()}` rather than `onAction={controller.close}`. A codemod does both. It wraps every bare reference (`close`, `controller.close`), because the wrap is a no-op for a reference that did not need it. It leaves a value that already is the handler or produces one — an arrow function, a function expression, a call like `makeHandler()` or `close.bind(controller)` — and anything that is not one reference, such as `isOpen ? close : open` or `controller?.close`. Two wraps to look at afterwards: a handler that read the event `Action` forwards stops receiving it, and a possibly-undefined reference (`onAction={props.onAction}`) becomes a call TypeScript rejects — add the guard it asks for.",
     },
     {
         id: "button-props-interfaces",
@@ -215,8 +242,8 @@ export const migrations = [
         since: "0.1.0-alpha.292",
         title: "Renamed CSS export",
         kind: "migration",
-        action: "manual",
+        action: "codemod",
         remotePackage: false,
-        apply: "Replace the import `@mittwald/flow-react-components/styles` with `@mittwald/flow-react-components/all.css`.",
+        apply: "Replace the import `@mittwald/flow-react-components/styles` with `@mittwald/flow-react-components/all.css`. A codemod does this for JavaScript and TypeScript files. An `@import` of the old path inside a `.css` or `.scss` file is not covered — search for it by hand.",
     },
 ];

package/dist/resolve/range.d.ts

@@ -47,4 +47,3 @@ export type RangeResult = ResolvedRange | UnresolvedRange;
  * fine; two callers computing the fact differently is how they drift.
  */
 export declare const resolveRange: (revision: string, deps: RangeDeps) => Promise<RangeResult>;
-//# sourceMappingURL=range.d.ts.map

package/dist/resolve/registry.d.ts

@@ -30,4 +30,3 @@ export declare const fetchAllVersions: (names: string[], fetchOne: (name: string
  * the intersection, not any single package's list.
  */
 export declare const intersectVersions: (packages: PackageVersions[]) => string[];
-//# sourceMappingURL=registry.d.ts.map

package/dist/resolve/target.d.ts

@@ -60,4 +60,3 @@ export type ResolveTargetResult = {
  * stable line never drifts onto the collection branch.
  */
 export declare const resolveTarget: ({ revision, current, versions, distTags, }: ResolveTargetInput) => ResolveTargetResult;
-//# sourceMappingURL=target.d.ts.map