rman 0.37.4 → 1.0.1

package/services/clean.service.js

@@ -0,0 +1,226 @@
+import fs from 'node:fs';
+import path from 'node:path';
+import colors from 'ansi-colors';
+import fg from 'fast-glob';
+import { Logger, resolveRootLogLevel } from '../utils/logger.js';
+import { filterPackages } from '../utils/package-filter.js';
+import { ProgressPanel } from '../utils/progress-panel.js';
+export var CleanService;
+(function (CleanService) {
+    /**
+     * `clean`: removes build output across every package (root included) - the built-in replacement
+     * for `ts-cleanup`, plus whatever else `.rmanrc clean.include`/`clean.exclude` says to remove.
+     *
+     * For every package not opted out via its own (cascaded) `clean.skip: true`:
+     *  - deletes compiled `.js`/`.js.map`/`.d.ts` files under its `src`/`test` (see `cleanTsArtifacts`);
+     *  - deletes any `*.tsbuildinfo` incremental-build cache file anywhere in it;
+     *  - deletes anything matching its own (cascaded) `clean.include` glob(s), minus `clean.exclude`.
+     *
+     * `include`/`exclude` are resolved relative to *that* package's own directory - a root-level
+     * `.rmanrc` pattern like `packages/*\/build` is naturally evaluated from the repository root
+     * (spanning every package in one pass), while a package's own override in its own `.rmanrc`
+     * (e.g. `include: ./cache`) only ever reaches that one package, since a package normally
+     * overrides rather than merges with the root's value for the same key.
+     *
+     * Never touches `node_modules` - that's `ci`'s job, not this one.
+     *
+     * Run from inside a single package's own directory, it only cleans that package unless
+     * `options.root` says otherwise (see `Repository.currentPackage`).
+     *
+     * Uses the same live progress panel as `run`/`build` (see `../utils/progress-panel.ts`) - unlike
+     * `ci`, cleaning genuinely is independent per-package work, so the final per-package tally stays.
+     */
+    async function clean(repository, options = {}) {
+        /** Standing inside a single package's own directory scopes cleaning to just that package
+         *  (root's own artifacts included) unless `--root` asks for the whole repository anyway - a
+         *  no-op when already at the root, or outside any known package. */
+        const cwdScope = options.root ? undefined : repository.currentPackage;
+        const packages = repository.getPackages().filter(p => p !== repository.rootPackage);
+        const allTargets = cwdScope ? [cwdScope] : [repository.rootPackage, ...packages];
+        const targets = filterPackages(allTargets, options).filter(pkg => !cleanConfig(pkg).skip);
+        const dryRun = options.dryRun ?? false;
+        const progress = options.progress ?? true;
+        const logger = new Logger(options.logLevel ?? resolveRootLogLevel(repository));
+        const panel = new ProgressPanel(dryRun ? 'CLEAN (dry-run)' : 'CLEAN', !!process.stdout.isTTY && progress);
+        panel.start();
+        let failed = false;
+        try {
+            const results = await Promise.allSettled(targets.map(pkg => {
+                const label = pkg === repository.rootPackage ? 'root' : pkg.name;
+                return cleanPackage(pkg, panel.addItem(label), panel.enabled, dryRun, logger);
+            }));
+            if (results.some(r => r.status === 'rejected'))
+                failed = true;
+        }
+        finally {
+            panel.stop();
+        }
+        panel.printSummary();
+        if (failed) {
+            const err = new Error('"clean" failed');
+            err.logged = true;
+            throw err;
+        }
+    }
+    CleanService.clean = clean;
+})(CleanService || (CleanService = {}));
+/** Directories a package's TypeScript output gets cleaned from, mirroring `ts-cleanup -s src`
+ *  and `-s test` (the only way it was ever actually invoked in this project's own scripts). */
+const TS_SOURCE_DIRS = ['src', 'test'];
+/** A package's (cascaded) `.rmanrc clean.include`/`clean.exclude`/`clean.skip` - a package that
+ *  declares its own `clean` block replaces the root's entirely for itself (same as any other
+ *  rman config key), rather than combining with it. `include`/`exclude` accept a single glob
+ *  string or an array of them. */
+function cleanConfig(pkg) {
+    const cfg = pkg.config?.clean;
+    const normalize = (v) => {
+        if (Array.isArray(v))
+            return v.map(String);
+        return typeof v === 'string' && v ? [v] : [];
+    };
+    return { include: normalize(cfg?.include), exclude: normalize(cfg?.exclude), skip: cfg?.skip === true };
+}
+/** Deletes `file`, unless `dryRun` - either way the caller treats it as removed for reporting. */
+async function remove(file, dryRun) {
+    if (!dryRun)
+        await fs.promises.rm(file, { force: true });
+}
+/** Removes now-empty directories under `dir`, deepest first (so a parent left empty once its
+ *  only child is removed gets caught in the same pass). Also removes `dir` itself once empty
+ *  when `includeSelf` is set - used when `dir` is itself something the user asked to delete
+ *  (e.g. an `include: build` match), as opposed to a source root like `src`/`test` that should
+ *  stay even if everything inside it was cleaned out. No-op in dry-run mode: nothing was actually
+ *  deleted, so there's nothing that could have been left empty. */
+function pruneEmptyDirs(dir, includeSelf, dryRun) {
+    if (dryRun || !fs.existsSync(dir))
+        return;
+    const entries = fg.sync('**', { cwd: dir, onlyDirectories: true, dot: true });
+    entries.sort((a, b) => b.split(path.sep).length - a.split(path.sep).length);
+    for (const rel of entries) {
+        const abs = path.join(dir, rel);
+        if (fs.existsSync(abs) && fs.readdirSync(abs).length === 0)
+            fs.rmdirSync(abs);
+    }
+    if (includeSelf && fs.readdirSync(dir).length === 0)
+        fs.rmdirSync(dir);
+}
+/**
+ * Deletes every path matched by `include` (minus `exclude`) under `dirname` - files and
+ * directories alike, gulp-`src()`-style. Returns what was actually removed (or, in dry-run mode,
+ * what *would* be), relative to `dirname`, so the caller only logs what really happened.
+ *
+ * `exclude` protects at two levels: a pattern matching a whole `include` result directly (e.g.
+ * `packages/pkg1/*` against a matched `packages/pkg1/build` directory) drops that result before
+ * anything under it is touched; a finer pattern (e.g. `build/*.json`) instead protects just the
+ * matching files *inside* an otherwise-deleted directory, leaving the rest of it gone and the
+ * protected files (and their now non-empty parent) in place.
+ */
+async function cleanGlobs(dirname, include, exclude, dryRun) {
+    if (!include.length)
+        return [];
+    const matches = await fg(include, { cwd: dirname, ignore: exclude, onlyFiles: false, dot: true, absolute: true });
+    const protectedFiles = exclude.length
+        ? new Set(await fg(exclude, { cwd: dirname, onlyFiles: true, dot: true, absolute: true }))
+        : new Set();
+    const removed = [];
+    for (const m of matches) {
+        const stat = await fs.promises.stat(m).catch(() => undefined);
+        if (!stat)
+            continue;
+        if (stat.isDirectory()) {
+            const filesInside = await fg('**', { cwd: m, onlyFiles: true, dot: true, absolute: true });
+            for (const f of filesInside) {
+                if (protectedFiles.has(f))
+                    continue;
+                await remove(f, dryRun);
+                removed.push(path.relative(dirname, f));
+            }
+            pruneEmptyDirs(m, true, dryRun);
+        }
+        else if (!protectedFiles.has(m)) {
+            await remove(m, dryRun);
+            removed.push(path.relative(dirname, m));
+        }
+    }
+    return removed;
+}
+/**
+ * Removes compiled TypeScript output (`.js`, `.js.map`, `.d.ts`) sitting next to its `.ts`
+ * source under `src`/`test` - the same job `ts-cleanup -s <dir> --all` did (the only mode this
+ * project ever actually used it in). A `.d.ts` with no matching `.ts`/`.tsx` is left alone - it's
+ * presumably a hand-written declaration file, not build output. Prunes directories left empty
+ * afterward.
+ */
+async function cleanTsArtifacts(dirname, dryRun) {
+    const removed = [];
+    for (const sub of TS_SOURCE_DIRS) {
+        const dir = path.join(dirname, sub);
+        if (!fs.existsSync(dir))
+            continue;
+        const files = await fg('**/*.{js,js.map,d.ts}', { cwd: dir, onlyFiles: true, dot: true, absolute: true });
+        for (const f of files) {
+            if (f.endsWith('.d.ts')) {
+                const base = f.slice(0, -'.d.ts'.length);
+                if (!fs.existsSync(base + '.ts') && !fs.existsSync(base + '.tsx'))
+                    continue;
+            }
+            await remove(f, dryRun);
+            removed.push(path.relative(dirname, f));
+        }
+        pruneEmptyDirs(dir, false, dryRun);
+    }
+    return removed;
+}
+/**
+ * Removes TypeScript's incremental-build cache files (`*.tsbuildinfo`) anywhere under `dirname` -
+ * `tsc --build`/`composite`/`incremental` output that `ts-cleanup` never touched, but which can
+ * leave a project in a stale state if a clean rebuild is expected to start from nothing. Skips
+ * `node_modules` (dependencies may ship their own, irrelevant to this package's own build).
+ */
+async function cleanTsBuildInfo(dirname, dryRun) {
+    const files = await fg('**/*.tsbuildinfo', {
+        cwd: dirname,
+        ignore: ['**/node_modules/**'],
+        onlyFiles: true,
+        dot: true,
+        absolute: true,
+    });
+    for (const f of files)
+        await remove(f, dryRun);
+    return files.map(f => path.relative(dirname, f));
+}
+async function cleanPackage(pkg, item, panelEnabled, dryRun, logger) {
+    item.status = 'running';
+    item.startedAt = Date.now();
+    try {
+        item.currentStep = 'ts';
+        const tsRemoved = await cleanTsArtifacts(pkg.dirname, dryRun);
+        const buildInfoRemoved = await cleanTsBuildInfo(pkg.dirname, dryRun);
+        item.currentStep = 'glob';
+        const { include, exclude } = cleanConfig(pkg);
+        const globRemoved = await cleanGlobs(pkg.dirname, include, exclude, dryRun);
+        const removed = [...tsRemoved, ...buildInfoRemoved, ...globRemoved];
+        const verb = dryRun ? 'would rm' : 'rm';
+        if (panelEnabled) {
+            item.lastLine = removed.length
+                ? `${dryRun ? 'would remove' : 'removed'} ${removed.length} item(s)`
+                : 'already clean';
+        }
+        else if (removed.length) {
+            for (const r of removed)
+                logger.info(colors.yellow(verb), colors.cyan(item.name), r);
+        }
+        else {
+            logger.info(colors.gray('clean'), colors.cyan(item.name));
+        }
+        item.status = 'success';
+    }
+    catch (e) {
+        item.status = 'failed';
+        item.log.push(e?.message ?? String(e));
+        throw e;
+    }
+    finally {
+        item.finishedAt = Date.now();
+    }
+}

package/services/exec.service.d.ts

@@ -0,0 +1,35 @@
+import type { Repository } from '../core/repository.js';
+import { type LogLevel } from '../utils/logger.js';
+import { type PackageFilterOptions } from '../utils/package-filter.js';
+export declare namespace ExecService {
+    interface Options extends PackageFilterOptions {
+        /** Max packages at once: `true`/omitted = CPU count, a number = that many, `false` = serial (1). */
+        parallel?: boolean | number;
+        /** Respect the package dependency graph: a package waits for its dependencies and is skipped
+         *  if one fails. Default true. Set false to run in every matching package independently,
+         *  alphabetically, regardless of the dependency graph. */
+        topo?: boolean;
+        bail?: boolean;
+        changed?: boolean;
+        changedSince?: string;
+        /** Show the live progress panel. Default true; auto-disabled when stdout isn't a TTY. */
+        progress?: boolean;
+        /** Verbosity of the classic per-package log (only applies when the live panel is off). Falls
+         *  back to the root's `.rmanrc logLevel`, then 'info' - see `resolveRootLogLevel`. */
+        logLevel?: LogLevel;
+        /** Run across the whole repository even when the current directory is inside a single package
+         *  (which otherwise scopes the run to just that package). Has no effect when already at the
+         *  repository root, or outside any known package. */
+        root?: boolean;
+    }
+    /**
+     * `exec`: runs `command` (an arbitrary shell command, not an npm script) directly in every
+     * matching package's own directory - unlike `run`, there's no `package.json` script to resolve
+     * and no `pre<script>`/`post<script>` npm lifecycle convention to honor, since the command isn't
+     * tied to any script name at all. Everything else about how packages are selected and scheduled
+     * matches `run`: topological order and per-package bail by default, the same live progress panel
+     * (falling back to a classic one-line-per-package log when it's off), and the same
+     * `--scope`/`--ignore`/`--deps`/`--dependents`/`--changed` package filtering.
+     */
+    function exec(repository: Repository, command: string, options?: Options): Promise<void>;
+}

package/services/exec.service.js

@@ -0,0 +1,114 @@
+import os from 'node:os';
+import colors from 'ansi-colors';
+import { Task } from 'power-tasks';
+import { exec as execCommand } from '../utils/exec.js';
+import { Logger, resolveRootLogLevel } from '../utils/logger.js';
+import { filterPackages } from '../utils/package-filter.js';
+import { ProgressPanel } from '../utils/progress-panel.js';
+export var ExecService;
+(function (ExecService) {
+    /**
+     * `exec`: runs `command` (an arbitrary shell command, not an npm script) directly in every
+     * matching package's own directory - unlike `run`, there's no `package.json` script to resolve
+     * and no `pre<script>`/`post<script>` npm lifecycle convention to honor, since the command isn't
+     * tied to any script name at all. Everything else about how packages are selected and scheduled
+     * matches `run`: topological order and per-package bail by default, the same live progress panel
+     * (falling back to a classic one-line-per-package log when it's off), and the same
+     * `--scope`/`--ignore`/`--deps`/`--dependents`/`--changed` package filtering.
+     */
+    async function exec(repository, command, options = {}) {
+        const logLevelDefault = resolveRootLogLevel(repository);
+        const logger = new Logger(options.logLevel ?? logLevelDefault);
+        const cwdScope = options.root ? undefined : repository.currentPackage;
+        const topo = options.topo ?? true;
+        let packages = repository.getPackages({ toposort: topo, scope: cwdScope?.name });
+        if (!topo)
+            packages = [...packages].sort((a, b) => a.name.localeCompare(b.name));
+        packages = filterPackages(packages, options);
+        if (options.changed || options.changedSince) {
+            const status = await repository.listStatus({ hash: options.changedSince });
+            packages = packages.filter(p => status[p.name] !== 'clean');
+        }
+        if (!packages.length) {
+            logger.info(colors.gray('No package matched.'));
+            return;
+        }
+        const concurrency = options.parallel === false
+            ? 1
+            : typeof options.parallel === 'number'
+                ? options.parallel
+                : options.parallel === true
+                    ? os.cpus().length
+                    : os.cpus().length;
+        const progress = options.progress ?? true;
+        const panel = new ProgressPanel('EXEC', !!process.stdout.isTTY && progress);
+        const bail = options.bail ?? true;
+        let rootTask;
+        const names = new Set(packages.map(p => p.name));
+        const children = packages.map(pkg => {
+            const ctx = panel.addItem(pkg.name);
+            const dependencies = topo ? pkg.dependencies.filter(d => names.has(d)) : [];
+            return new Task(() => execForPackage(ctx, panel.enabled, pkg.dirname, command, logger, bail ? () => rootTask?.abort() : () => { }), { name: pkg.name, dependencies });
+        });
+        panel.start();
+        let failed = false;
+        try {
+            /** bail:false here - each item's own task decides whether to call `rootTask.abort()`
+             *  itself (see `execForPackage`), mirroring `run`'s own reasoning: power-tasks' own `bail`
+             *  is a single blanket policy, it can't be conditional on `options.bail`. `toPromise()`
+             *  still rejects on any child's failure regardless, whether or not it triggered an abort. */
+            rootTask = new Task(children, { concurrency, bail: false });
+            await rootTask.toPromise();
+        }
+        catch {
+            failed = true;
+        }
+        finally {
+            panel.stop();
+        }
+        panel.printSummary();
+        if (failed) {
+            const err = new Error('"exec" failed');
+            err.logged = true;
+            throw err;
+        }
+    }
+    ExecService.exec = exec;
+})(ExecService || (ExecService = {}));
+async function execForPackage(ctx, panelEnabled, cwd, command, logger, abort) {
+    ctx.status = 'running';
+    ctx.startedAt = Date.now();
+    try {
+        if (panelEnabled) {
+            await execCommand(command, {
+                cwd,
+                stdio: 'pipe',
+                onLine: line => {
+                    ctx.log.push(line);
+                    ctx.lastLine = line;
+                },
+            });
+        }
+        else {
+            logger.info(colors.cyan('exec'), colors.cyan(ctx.name), command);
+            const t = Date.now();
+            try {
+                await execCommand(command, { cwd, stdio: 'inherit' });
+                logger.info(colors.green('success'), colors.cyan(ctx.name), colors.yellow(`(${Date.now() - t} ms)`));
+            }
+            catch (e) {
+                logger.error(colors.red('failed'), colors.cyan(ctx.name), colors.yellow(`(${Date.now() - t} ms)`));
+                throw e;
+            }
+        }
+        ctx.status = 'success';
+    }
+    catch (e) {
+        ctx.status = 'failed';
+        abort();
+        throw e;
+    }
+    finally {
+        ctx.finishedAt = Date.now();
+    }
+}

package/services/import.service.d.ts

@@ -0,0 +1,30 @@
+import type { Repository } from '../core/repository.js';
+export declare namespace ImportService {
+    interface Options {
+        /** Subdirectory (relative to the repository root) the new package is placed under - default `'packages'`. */
+        dest?: string;
+    }
+    interface Result {
+        /** The imported package's name (from its own `package.json`, or its directory basename). */
+        name: string;
+        /** Where it was placed, absolute. */
+        targetDir: string;
+        commitCount: number;
+    }
+    /**
+     * Imports `sourcePath` (a local clone of some other git repository) as a new package under this
+     * repository, preserving its **entire commit history** - every original commit, author, date and
+     * message stays intact, just as if the package had always lived at its new path. Unlike copying
+     * the files over and making one "import" commit, `git blame`/`git log --follow` keep working on
+     * the imported files afterward.
+     *
+     * How: every commit reachable from `sourcePath`'s HEAD is turned into a patch (`git format-patch
+     * --root`, oldest first), each patch's file paths are rewritten to be prefixed with the new
+     * subdirectory, then replayed onto this repository via `git am` (preserving authorship). A
+     * source repo with merge commits or binary-file renames can still trip up a patch here or there -
+     * same caveat `lerna import` has, since both use this same replay approach rather than a real
+     * merge (which real `git subtree` would give, at the cost of far less predictable behavior
+     * across git versions - the reason this - and lerna - avoid it).
+     */
+    function importRepo(repository: Repository, sourcePath: string, options?: Options): Promise<Result>;
+}

package/services/import.service.js

@@ -0,0 +1,84 @@
+import fs from 'node:fs';
+import os from 'node:os';
+import path from 'node:path';
+import { GitHelper } from '../utils/git.js';
+export var ImportService;
+(function (ImportService) {
+    /**
+     * Imports `sourcePath` (a local clone of some other git repository) as a new package under this
+     * repository, preserving its **entire commit history** - every original commit, author, date and
+     * message stays intact, just as if the package had always lived at its new path. Unlike copying
+     * the files over and making one "import" commit, `git blame`/`git log --follow` keep working on
+     * the imported files afterward.
+     *
+     * How: every commit reachable from `sourcePath`'s HEAD is turned into a patch (`git format-patch
+     * --root`, oldest first), each patch's file paths are rewritten to be prefixed with the new
+     * subdirectory, then replayed onto this repository via `git am` (preserving authorship). A
+     * source repo with merge commits or binary-file renames can still trip up a patch here or there -
+     * same caveat `lerna import` has, since both use this same replay approach rather than a real
+     * merge (which real `git subtree` would give, at the cost of far less predictable behavior
+     * across git versions - the reason this - and lerna - avoid it).
+     */
+    async function importRepo(repository, sourcePath, options = {}) {
+        const absSource = path.resolve(sourcePath);
+        if (!fs.existsSync(path.join(absSource, '.git'))) {
+            throw new Error(`"${sourcePath}" is not a git repository (no .git found) - clone it locally first`);
+        }
+        const name = resolveSourceName(absSource);
+        const dirName = name.includes('/') ? name.slice(name.lastIndexOf('/') + 1) : name;
+        const destDir = options.dest ?? 'packages';
+        const targetDir = path.join(repository.dirname, destDir, dirName);
+        if (fs.existsSync(targetDir)) {
+            throw new Error(`"${path.relative(repository.dirname, targetDir)}" already exists`);
+        }
+        const sourceGit = new GitHelper({ cwd: absSource });
+        const patchDir = fs.mkdtempSync(path.join(os.tmpdir(), 'rman-import-'));
+        try {
+            const patches = await sourceGit.formatPatches(patchDir);
+            if (!patches.length)
+                throw new Error(`"${sourcePath}" has no commits to import`);
+            const relTargetDir = path.relative(repository.dirname, targetDir).split(path.sep).join('/');
+            for (const patchFile of patches)
+                rewritePatchPaths(patchFile, relTargetDir);
+            const targetGit = new GitHelper({ cwd: repository.dirname });
+            await targetGit.applyPatches(patches);
+            return { name, targetDir, commitCount: patches.length };
+        }
+        finally {
+            fs.rmSync(patchDir, { recursive: true, force: true });
+        }
+    }
+    ImportService.importRepo = importRepo;
+})(ImportService || (ImportService = {}));
+/** The source repo's own `package.json` name, or its directory's basename when it has none (or
+ *  isn't even a package yet - a plain library repo being folded in). */
+function resolveSourceName(absSource) {
+    const pkgJsonFile = path.join(absSource, 'package.json');
+    if (fs.existsSync(pkgJsonFile)) {
+        try {
+            const json = JSON.parse(fs.readFileSync(pkgJsonFile, 'utf-8'));
+            if (typeof json.name === 'string' && json.name)
+                return json.name;
+        }
+        catch {
+            // malformed package.json - fall through to the directory name below.
+        }
+    }
+    return path.basename(absSource);
+}
+/**
+ * Rewrites a `git format-patch`-produced file in place so every path it touches is prefixed with
+ * `prefix` (the new subdirectory, forward-slash-separated) - `diff --git`/`---`/`+++`/rename
+ * headers only; `--- /dev/null`/`+++ /dev/null` (new/deleted file markers) never match, since they
+ * have no `a/`/`b/` prefix to rewrite in the first place.
+ */
+function rewritePatchPaths(patchFile, prefix) {
+    const content = fs.readFileSync(patchFile, 'utf-8');
+    const rewritten = content
+        .replace(/^diff --git a\/(.+?) b\/(.+)$/gm, (_m, a, b) => `diff --git a/${prefix}/${a} b/${prefix}/${b}`)
+        .replace(/^--- a\/(.+)$/gm, (_m, p) => `--- a/${prefix}/${p}`)
+        .replace(/^\+\+\+ b\/(.+)$/gm, (_m, p) => `+++ b/${prefix}/${p}`)
+        .replace(/^rename from (.+)$/gm, (_m, p) => `rename from ${prefix}/${p}`)
+        .replace(/^rename to (.+)$/gm, (_m, p) => `rename to ${prefix}/${p}`);
+    fs.writeFileSync(patchFile, rewritten);
+}

package/services/list.service.d.ts

@@ -0,0 +1,27 @@
+import type { Repository } from '../core/repository.js';
+import { type PackageFilterOptions } from '../utils/package-filter.js';
+export declare namespace ListService {
+    interface Options extends PackageFilterOptions {
+        /** Topological order (dependencies before dependents) instead of lexical by directory. */
+        toposort?: boolean;
+        /** Only include packages that have changed since the last publish (dirty or committed but
+         *  not yet published) - or, with `changedSince`, since that specific commit/hash. */
+        changed?: boolean;
+        changedSince?: string;
+    }
+    interface Item {
+        name: string;
+        version: string;
+        location: string;
+        private: boolean;
+        status: Repository.PackageStatus;
+        /** In-repo package names this one depends on - enough to build a dependency graph without a
+         *  second call, e.g. `Object.fromEntries(items.map(i => [i.name, i.dependencies]))`. */
+        dependencies: string[];
+    }
+    /** `list`: every package in the repository (or, with `changed`/`changedSince`, only the ones
+     *  that have actually changed), each with its version, location, private flag, and change
+     *  status relative to upstream. Pure data - no console output; `rman list`'s own command
+     *  decides how to present it (table, JSON, parseable, names only, or a dependency graph). */
+    function getPackages(repository: Repository, options?: Options): Promise<Item[]>;
+}

package/services/list.service.js

@@ -0,0 +1,25 @@
+import path from 'path';
+import { filterPackages } from '../utils/package-filter.js';
+export var ListService;
+(function (ListService) {
+    /** `list`: every package in the repository (or, with `changed`/`changedSince`, only the ones
+     *  that have actually changed), each with its version, location, private flag, and change
+     *  status relative to upstream. Pure data - no console output; `rman list`'s own command
+     *  decides how to present it (table, JSON, parseable, names only, or a dependency graph). */
+    async function getPackages(repository, options = {}) {
+        const packages = filterPackages(repository.getPackages({ toposort: options.toposort }), options);
+        const status = await repository.listStatus({ hash: options.changedSince });
+        let items = packages.map(p => ({
+            name: p.name,
+            version: p.version,
+            location: path.relative(repository.dirname, p.dirname) || '.',
+            private: p.isPrivate,
+            status: status[p.name],
+            dependencies: [...p.dependencies],
+        }));
+        if (options.changed || options.changedSince)
+            items = items.filter(it => it.status !== 'clean');
+        return items;
+    }
+    ListService.getPackages = getPackages;
+})(ListService || (ListService = {}));

package/services/publish.service.d.ts

@@ -0,0 +1,79 @@
+import type { Package } from '../core/package.js';
+import type { Repository } from '../core/repository.js';
+import { type PackageFilterOptions } from '../utils/package-filter.js';
+import { CiService } from './ci.service.js';
+export declare namespace PublishService {
+    /** Injectable registry lookup - mainly for tests, so they don't depend on network access or a
+     *  real published package. Same shape as `detectChangeHash`'s own `npmViewVersion`. */
+    interface Deps {
+        npmViewVersion?: (name: string, cwd: string) => Promise<string | undefined>;
+    }
+    interface Options extends PackageFilterOptions {
+        /** A package with uncommitted local changes is excluded (status `'skip'`) instead of aborting
+         *  the whole plan (status `'error'`) - same as `version`'s own option. Default false. */
+        ignoreDirty?: boolean;
+        /** Registry to check against (and, in `applyPlan`, publish to) - `.npmrc`'s own configured
+         *  registry is used when omitted. */
+        registry?: string;
+        /** Path to a custom `.npmrc`, for both the registry check and the actual publish. */
+        userconfig?: string;
+    }
+    interface ApplyOptions extends Options {
+        packageManager?: CiService.PackageManager;
+        /** `npm publish --access <access>` - required by the registry for a *new* scoped package. */
+        access?: 'public' | 'restricted';
+        /** `npm publish --tag <tag>` - the dist-tag this version is published under (default `latest`). */
+        tag?: string;
+        /** `npm publish --otp <otp>` - a 2FA one-time password, for registries that require it. */
+        otp?: string;
+        /** Subdirectory to publish from, relative to the package's own directory - only consulted when
+         *  the package doesn't already declare its own `package.json` `publishConfig.directory` (npm's
+         *  native mechanism for this, which always wins when present). */
+        contents?: string;
+    }
+    /** One package's outcome in a publish plan - see `getPlan`. */
+    interface Entry {
+        package: Package;
+        version: string;
+        status: 'publish' | 'skip' | 'up-to-date' | 'error';
+        /** What's currently on the registry, if anything - only set once a registry check actually ran. */
+        registryVersion?: string;
+        reason?: string;
+    }
+    /**
+     * Computes what `publish` *would* do, across every non-private package (topological order,
+     * dependencies before dependents) - never touches the registry to publish anything, just
+     * queries it to decide, so it's safe to call any time, including as the plan a bare `rman
+     * publish` shows before asking for confirmation.
+     *
+     * A `private: true` package is always `'skip'`ped outright. A package with uncommitted local
+     * changes is `'error'` (aborts the whole plan) unless `options.ignoreDirty` downgrades it to
+     * `'skip'` instead - same rule `version` uses, since publishing untracked local edits is worse
+     * than a bad commit. Otherwise, its currently-published registry version (via `npm view`,
+     * queried concurrently across every remaining package) decides the rest: identical to the local
+     * `package.json` version is `'up-to-date'`; anything else (including never having been
+     * published at all) is `'publish'`.
+     *
+     * Deliberately decoupled from `version`: this only ever looks at what's *currently* on disk and
+     * on the registry, never at whether `version` was just run - so it works equally well right
+     * after a version bump, or standing alone in a release pipeline that bumped days earlier.
+     *
+     * A monorepo's root package is never a candidate at all - `repository.getPackages()` already
+     * excludes it for a real monorepo (it only doubles as "the" package in a single-package repo,
+     * where it's a normal candidate like any other).
+     */
+    function getPlan(repository: Repository, options?: Options, deps?: Deps): Promise<Entry[]>;
+    /**
+     * Publishes every `'publish'` entry in `plan`, topological order (already `plan`'s own order -
+     * see `getPlan`), via the configured `packageManager`'s own `publish` command. Sequential, not
+     * concurrent: unlike `run`/`build`, a package genuinely needs its own dependencies to have
+     * landed on the registry first, and publishing is rare enough (once per release) that the
+     * simplicity is worth more than the parallelism `run` gets from `power-tasks`.
+     *
+     * If a package fails, every other still-pending entry depending on it (transitively) is marked
+     * `'error'` too and never attempted - publishing a package whose own new dependency range points
+     * at a version that never actually reached the registry would hand consumers a broken install.
+     * A package's own failure doesn't stop unrelated packages elsewhere in the plan, though.
+     */
+    function applyPlan(repository: Repository, plan: Entry[], options?: ApplyOptions): Promise<Entry[]>;
+}