@loopress/cli 0.33.0 → 0.35.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@loopress/cli",
   "description": "Build, review and ship WordPress, in one loop: pull, diff, push and roll back a site's code and config from git",
-  "version": "0.33.0",
+  "version": "0.35.0",
   "author": "jean-smaug",
   "bin": {
     "loopress": "bin/run.js",
@@ -11,22 +11,22 @@
     "url": "https://github.com/loopress/loopress/issues"
   },
   "dependencies": {
-    "@inquirer/prompts": "^8.7.4",
-    "@oclif/core": "^5.1.9",
-    "@oclif/plugin-help": "^7.0.5",
+    "@inquirer/prompts": "^8.7.5",
+    "@oclif/core": "^5.1.11",
+    "@oclif/plugin-help": "^7.0.6",
     "@oclif/plugin-warn-if-update-available": "^4.0.5",
-    "@sentry/node": "^11.9.0",
-    "chokidar": "^5.0.0",
+    "@sentry/node": "^11.11.0",
+    "chokidar": "^6.0.0",
     "compare-versions": "^6.1.1",
     "diff": "^9.0.0",
     "esbuild": "0.28.2",
-    "got": "^16.1.0",
+    "got": "^16.2.0",
     "listr2": "^11.4.0",
     "microdiff": "^1.6.0",
     "open": "^11.0.4",
     "playwright-core": "^1.64.1",
     "slugify": "^1.6.9",
-    "tty-table": "^5.0.0",
+    "tty-table": "^7.2.1",
     "write-file-atomic": "^8.0.0",
     "zod": "^4.6.7"
   },
@@ -34,23 +34,23 @@
     "@oclif/prettier-config": "^0.2.2",
     "@stryker-mutator/core": "^10.1.1",
     "@stryker-mutator/vitest-runner": "^10.1.1",
-    "@types/node": "26.6.5",
+    "@types/node": "26.6.6",
     "@types/write-file-atomic": "^4.0.3",
-    "@vitest/coverage-v8": "^4.1.11",
+    "@vitest/coverage-v8": "^5.1.0",
     "@vitest/eslint-plugin": "^1.6.28",
-    "eslint": "^10.13.0",
+    "eslint": "^10.14.0",
     "eslint-config-oclif": "^7.1.10",
     "eslint-config-prettier": "^10",
-    "eslint-plugin-regexp": "^3.3.1",
+    "eslint-plugin-regexp": "^3.3.3",
     "eslint-plugin-sonarjs": "^4.2.2",
     "json-schema-to-typescript": "^16.0.0",
-    "oclif": "^6.0.10",
+    "oclif": "^6.0.15",
     "prettier": "3.9.10",
     "shx": "^0.4.0",
     "ts-node": "10.9.2",
     "tsx": "4.23.15",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.11"
+    "vitest": "^5.1.0"
   },
   "engines": {
     "node": ">=22.0.0"

package/schemas/project-config.schema.json

@@ -39,12 +39,12 @@
       "description": "Directory of dynamic blocks, one <slug>/ folder holding block.json and render.php, registered as loopress/<slug>, relative to rootDir.",
       "default": "blocks"
     },
-    "hooksDir": {
+    "hookDir": {
       "type": "string",
       "description": "Directory where hook files (WordPress actions, filters, and scheduled tasks) are read from and written to, relative to rootDir.",
       "default": "hooks"
     },
-    "appsDir": {
+    "appDir": {
       "type": "string",
       "description": "Directory where single-page app bundles are read from and written to, relative to rootDir. Each subdirectory is one app: a loopress.app.json plus a built dist/ folder.",
       "default": "apps"
@@ -74,7 +74,7 @@
       "description": "Directory of per-block CSS (one <namespace>/<block>.css per block, e.g. core/button.css), relative to rootDir. Each file is bundled into the Loopress child theme and only loaded on pages that render that block.",
       "default": "theme/blocks"
     },
-    "optionsDir": {
+    "optionDir": {
       "type": "string",
       "description": "Directory where explicitly tracked WordPress options (wp_options rows) are read from and written to, relative to rootDir. Only options added via `lps option add` live here, this is never the whole options table.",
       "default": "options"
@@ -109,7 +109,7 @@
       "description": "Directory where nav menus (one JSON file per menu, plus menu-locations.json for the active theme's menu locations) are read from and written to, relative to rootDir.",
       "default": "menus"
     },
-    "themeStylesDir": {
+    "themeStyleDir": {
       "type": "string",
       "description": "Directory where the active block theme's Global Styles customizations (Site Editor > Styles: colors, typography, spacing) are read from and written to, relative to rootDir. Classic (non-block) themes are not supported.",
       "default": "theme"
@@ -143,6 +143,23 @@
         }
       ]
     },
+    "environments": {
+      "type": "object",
+      "description": "Per-environment settings, keyed by environment name (as in `lps project config`).",
+      "additionalProperties": {
+        "type": "object",
+        "additionalProperties": false,
+        "properties": {
+          "exclude": {
+            "type": "array",
+            "description": "Globs relative to rootDir (`*`, `**`, `?`) of files this environment never receives. `lps push`, `lps diff` and `lps promote` leave them alone on it: never pushed, never pruned or mirrored away, reported as held back instead of drift. A glob matching a directory covers everything inside. `lps pull` and `lps dev` ignore it.",
+            "items": {"type": "string"},
+            "examples": [["cpt/vocabulary-games.json", "theme/templates/*-vocabulary-games.html"]]
+          }
+        }
+      },
+      "examples": [{"production": {"exclude": ["hooks/vocabulary-games-page.php"]}}]
+    },
     "activateChildTheme": {
       "type": "boolean",
       "description": "Keep the Loopress child theme (<parent>-loopress) active: `lps theme template push`, and so `lps push`, activates it when it isn't. Off by default, a theme switch changes the settings WordPress stores per theme.",

package/dist/commands/api/publish.d.ts

@@ -1,9 +0,0 @@
-import { Command } from '@oclif/core';
-export default class Publish extends Command {
-    static args: {
-        path: import("@oclif/core/interfaces").Arg<string | undefined, Record<string, unknown>>;
-    };
-    static description: string;
-    static examples: string[];
-    run(): Promise<void>;
-}

package/dist/commands/api/publish.js

@@ -1,45 +0,0 @@
-import { Args, Command } from '@oclif/core';
-import { basename, join } from 'node:path';
-import { ApiClient } from '../../lib/api-client.js';
-import { loadFiles } from '../../lib/load-files.js';
-import { errorMessage } from '../../lib/narrow.js';
-import { resolveLinkedProject } from '../../lib/resolve-linked-project.js';
-import { pluralize } from '../../utils/pluralize.js';
-// Publishes to the Loopress api (not a WordPress site), so this does not extend
-// `LoopressCommand`/`PushCommand`: those force an environment to be resolved, but publishing
-// for cross-project sharing doesn't need one, same reasoning as `snippet publish`. An API route
-// is a special case of the same publish/deploy rules as snippets and ACF (see
-// obsidian/Product/API and Console Backlog.md, US-18): a `push` (direct to WordPress, this
-// project's own site) and a `publish` (to the cloud, deployable to other projects) are two
-// separate, coexisting paths.
-export default class Publish extends Command {
-    static args = {
-        path: Args.string({ description: 'Path to api directory (overrides project config)' }),
-    };
-    static description = 'Publish custom API routes to your Loopress account so they can be deployed to other projects. Does not touch any WordPress site.';
-    static examples = ['$ lps api publish', '$ lps api publish ./api'];
-    async run() {
-        const { args } = await this.parse(Publish);
-        const { apiProjectId, localConfig, token } = await resolveLinkedProject((message) => this.error(message));
-        const path = args.path ?? join(localConfig.rootDir ?? '.', localConfig.apiDir ?? 'api');
-        this.log(`Publishing API routes from ${path}`);
-        const files = await loadFiles(path, {
-            extension: '.php',
-            onSkip: (message) => { this.warn(message); },
-            parse: (raw, filePath) => ({ code: raw, filename: basename(filePath, '.php') }),
-        });
-        const api = new ApiClient(token);
-        try {
-            await api.post(`projects/${apiProjectId}/api-routes/publish/upsert`, {
-                routes: files,
-            });
-            await api.post(`projects/${apiProjectId}/api-routes/publish/prune`, {
-                filenames: files.map((file) => file.filename),
-            });
-        }
-        catch (error) {
-            this.error(errorMessage(error));
-        }
-        this.log(`Published ${pluralize(files.length, 'route')} to your Loopress account.`);
-    }
-}

package/dist/commands/snippet/publish.d.ts

@@ -1,10 +0,0 @@
-import { Command } from '@oclif/core';
-export default class Publish extends Command {
-    static args: {
-        path: import("@oclif/core/interfaces").Arg<string | undefined, Record<string, unknown>>;
-    };
-    static description: string;
-    static examples: string[];
-    run(): Promise<void>;
-    private toPayload;
-}

package/dist/commands/snippet/publish.js

@@ -1,62 +0,0 @@
-import { Args, Command } from '@oclif/core';
-import { ApiClient } from '../../lib/api-client.js';
-import { loadSnippets } from '../../lib/load-snippets.js';
-import { errorMessage } from '../../lib/narrow.js';
-import { resolveLinkedProject } from '../../lib/resolve-linked-project.js';
-import {} from '../../types/snippet.js';
-import { pluralize } from '../../utils/pluralize.js';
-import { resolveResourceDir } from '../../utils/resource-dirs.js';
-import { toSlug } from '../../utils/to-slug.js';
-// Publishes to the Loopress api (not a WordPress site), so this does not extend
-// `LoopressCommand`/`PushCommand`: those force an environment to be resolved, but a project
-// publishing its snippets for sharing doesn't need one, a pure "library" project 
-// may have zero environments configured at all.
-export default class Publish extends Command {
-    static args = {
-        path: Args.string({ description: 'Path to snippets directory (overrides project config)' }),
-    };
-    static description = 'Publish snippets to your Loopress account so they can be deployed to other projects. Does not touch any WordPress site.';
-    static examples = ['$ lps snippet publish', '$ lps snippet publish ./snippets'];
-    async run() {
-        const { args } = await this.parse(Publish);
-        const { apiProjectId, localConfig, token } = await resolveLinkedProject((message) => this.error(message));
-        const path = resolveResourceDir('snippets', localConfig, args.path);
-        this.log(`Publishing snippets from ${path}`);
-        let snippets;
-        try {
-            snippets = await loadSnippets(path, (message) => {
-                this.warn(message);
-            });
-        }
-        catch (error) {
-            this.error(errorMessage(error));
-        }
-        const api = new ApiClient(token);
-        try {
-            await api.post(`projects/${apiProjectId}/snippets/publish`, {
-                snippets: snippets.map((snippet) => this.toPayload(snippet)),
-            });
-        }
-        catch (error) {
-            this.error(errorMessage(error));
-        }
-        this.log(`Published ${pluralize(snippets.length, 'snippet')} to your Loopress account.`);
-    }
-    toPayload(snippet) {
-        return {
-            active: snippet.active,
-            code: snippet.code,
-            insertMethod: snippet.insertMethod,
-            location: snippet.location,
-            name: snippet.name,
-            priority: snippet.priority,
-            shortcodeAttributes: snippet.shortcodeAttributes,
-            // Derived from the snippet's name rather than its on-disk filename: the same
-            // slugification `push`/`pull` already use for the canonical `<id>-<slug>` filename
-            // convention, so it stays stable even for a not-yet-pushed file with an arbitrary name.
-            slug: toSlug(snippet.name),
-            tags: snippet.tags,
-            type: snippet.type,
-        };
-    }
-}

package/dist/lib/resolve-linked-project.d.ts

@@ -1,8 +0,0 @@
-import { type LoopressLocalConfig } from '../utils/loopress-config.js';
-type LinkedProject = {
-    apiProjectId: string;
-    localConfig: LoopressLocalConfig;
-    token: string;
-};
-export declare function resolveLinkedProject(fail: (message: string) => never): Promise<LinkedProject>;
-export {};

package/dist/lib/resolve-linked-project.js

@@ -1,27 +0,0 @@
-import { authManager } from '../config/auth.manager.js';
-import { configManager } from '../config/project-config.manager.js';
-import { readLocalConfig } from '../utils/loopress-config.js';
-// Shared preamble for `api publish` and `snippet publish`. Both target the Loopress cloud (never
-// a WordPress site), so neither extends `LoopressCommand`/`PushCommand` and neither needs an
-// environment resolved, but both need a logged-in user and a project already linked to the
-// account (`lps project push`). `fail` is the caller's `this.error`, so its messages keep
-// oclif's formatting and exit code; typed `=> never` so callers still narrow after the guards.
-export async function resolveLinkedProject(fail) {
-    const token = process.env.LOOPRESS_TOKEN ?? authManager.getAuth()?.token;
-    if (!token) {
-        fail('Not logged in. Run `lps login` first.');
-    }
-    const localConfig = await readLocalConfig();
-    const projectId = localConfig.projectId ?? configManager.getCurrentProject()?.id;
-    if (!projectId) {
-        fail('No project configured. Run `lps project config` first.');
-    }
-    const project = configManager.getProject(projectId);
-    if (!project) {
-        fail(`Project "${projectId}" (from loopress.json) not found. Run \`lps project config\` to configure it.`);
-    }
-    if (!project.apiProjectId) {
-        fail(`Project "${project.name}" is not linked to your Loopress account yet. Run \`lps project push\` first.`);
-    }
-    return { apiProjectId: project.apiProjectId, localConfig, token };
-}