velora-plugin 0.9.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,22 @@
+# velora-plugin
+
+The CLI for building, validating, packing, and publishing Velora plugins.
+Validates a plugin's manifest, required views, TypeScript compilation,
+bundle size, and Module Federation shared-dependency setup before it can
+be packed into a tarball or submitted to the marketplace.
+
+## Install
+
+```sh
+npm install --save-dev velora-plugin
+```
+
+## Usage
+
+```sh
+npx velora-plugin validate
+npx velora-plugin build
+npx velora-plugin pack
+```
+
+Part of [Velora](https://github.com/velora-cms/velora). Apache-2.0.

package/dist/build-federation-bundle.d.ts

@@ -0,0 +1,29 @@
+export interface FederationBuildResult {
+    outDir: string;
+    remoteEntryPath: string | null;
+    buildError?: string;
+}
+/**
+ * Builds a plugin's Module Federation bundle into an isolated temp
+ * directory, for measurement only (bundle size, shared-deps checks) —
+ * never the plugin's own dist/. Caller must call cleanupFederationBuild.
+ *
+ * NOT safe to call concurrently within one process — see
+ * runFederationBuild's process-global mutation. Callers must await one
+ * call to completion before starting another.
+ */
+export declare function buildFederationBundle(pluginDir: string): Promise<FederationBuildResult>;
+export declare function cleanupFederationBuild(result: FederationBuildResult): void;
+/**
+ * Runs the same real Vite Module Federation build as
+ * buildFederationBundle, but into a PERMANENT, caller-supplied `outDir`
+ * — no temp directory, no cleanup. Used by `velora-plugin build`
+ * (Session 81) to produce the real, distributable remoteEntry.js.
+ *
+ * NOT safe to call concurrently within one process, for the same reason
+ * as buildFederationBundle.
+ */
+export declare function buildFederationBundleTo(pluginDir: string, outDir: string): Promise<{
+    remoteEntryPath: string | null;
+    buildError?: string;
+}>;

package/dist/build-federation-bundle.js

@@ -0,0 +1,93 @@
+import { mkdirSync, mkdtempSync, readdirSync, rmSync } from "node:fs";
+import { tmpdir } from "node:os";
+import { join, resolve } from "node:path";
+import { build } from "vite";
+/**
+ * Shared core: runs a real Vite Module Federation build for
+ * `absolutePluginDir` into `outDir` (already resolved, already
+ * existing), applying both real @module-federation/vite workarounds
+ * this session discovered (cwd-relative `exposes` resolution,
+ * `isTestEnv()` bailout under Vitest). NOT safe to call concurrently —
+ * see the two public wrappers' own docs.
+ */
+async function runFederationBuild(absolutePluginDir, outDir) {
+    const previousCwd = process.cwd();
+    const previousNoTestEnvCheck = process.env.MFE_VITE_NO_TEST_ENV_CHECK;
+    try {
+        // @module-federation/vite resolves each `exposes` entry (e.g. "./src/plugin.tsx")
+        // relative to process.cwd() when generating its virtual remoteEntry module —
+        // not relative to Vite's `root`/`configFile` options. Without matching cwd to
+        // pluginDir, the build fails with "Could not resolve './src/plugin.tsx'" for
+        // every scaffolded/first-party plugin (both use relative exposes paths).
+        process.chdir(absolutePluginDir);
+        // @module-federation/vite's federation() plugin factory has a built-in
+        // isTestEnv() bailout — `if (NODE_ENV === "test" || VITEST != null ||
+        // JEST_WORKER_ID != null) return [];` — that silently drops itself from the
+        // plugin list with no error, so the build quietly falls back to a plain
+        // index.html build with no remoteEntry.js. Both this package's own test
+        // suite (Vitest) and a real `velora-plugin build` CLI invocation run this
+        // function, so the escape hatch is applied unconditionally — it's a no-op
+        // outside a test runner, since VITEST/NODE_ENV=test are never set there.
+        process.env.MFE_VITE_NO_TEST_ENV_CHECK = "true";
+        await build({
+            root: absolutePluginDir,
+            configFile: join(absolutePluginDir, "vite.config.ts"),
+            logLevel: "silent",
+            build: { outDir, emptyOutDir: true },
+        });
+    }
+    catch (error) {
+        return { remoteEntryPath: null, buildError: error instanceof Error ? error.message : String(error) };
+    }
+    finally {
+        process.chdir(previousCwd);
+        if (previousNoTestEnvCheck === undefined) {
+            delete process.env.MFE_VITE_NO_TEST_ENV_CHECK;
+        }
+        else {
+            process.env.MFE_VITE_NO_TEST_ENV_CHECK = previousNoTestEnvCheck;
+        }
+    }
+    const remoteEntryName = readdirSync(outDir).find((file) => /^remoteEntry.*\.js$/.test(file));
+    return { remoteEntryPath: remoteEntryName ? join(outDir, remoteEntryName) : null };
+}
+/**
+ * Builds a plugin's Module Federation bundle into an isolated temp
+ * directory, for measurement only (bundle size, shared-deps checks) —
+ * never the plugin's own dist/. Caller must call cleanupFederationBuild.
+ *
+ * NOT safe to call concurrently within one process — see
+ * runFederationBuild's process-global mutation. Callers must await one
+ * call to completion before starting another.
+ */
+export async function buildFederationBundle(pluginDir) {
+    const absolutePluginDir = resolve(pluginDir);
+    const outDir = mkdtempSync(join(tmpdir(), "velora-plugin-validate-"));
+    const result = await runFederationBuild(absolutePluginDir, outDir);
+    return { outDir, ...result };
+}
+export function cleanupFederationBuild(result) {
+    rmSync(result.outDir, { recursive: true, force: true });
+}
+/**
+ * Runs the same real Vite Module Federation build as
+ * buildFederationBundle, but into a PERMANENT, caller-supplied `outDir`
+ * — no temp directory, no cleanup. Used by `velora-plugin build`
+ * (Session 81) to produce the real, distributable remoteEntry.js.
+ *
+ * NOT safe to call concurrently within one process, for the same reason
+ * as buildFederationBundle.
+ */
+export async function buildFederationBundleTo(pluginDir, outDir) {
+    const absolutePluginDir = resolve(pluginDir);
+    // Vite resolves a relative build.outDir against `root` (absolutePluginDir
+    // above), not against the process's original cwd — if a caller passes a
+    // relative outDir (e.g. "plugins/google-maps/velora-package" from a CLI
+    // invoked with a relative pluginDir), the build silently doubles the path
+    // (".../plugins/google-maps/plugins/google-maps/velora-package"). Resolve
+    // once, up front, so this function is correct regardless of what shape of
+    // path a caller passes in.
+    const absoluteOutDir = resolve(outDir);
+    mkdirSync(absoluteOutDir, { recursive: true });
+    return runFederationBuild(absolutePluginDir, absoluteOutDir);
+}

package/dist/build.d.ts

@@ -0,0 +1,41 @@
+import type { FederationBuildResult } from "./build-federation-bundle.js";
+import type { ValidationResult } from "./types.js";
+export declare class BuildValidationError extends Error {
+    readonly validation: ValidationResult;
+    constructor(message: string, validation: ValidationResult);
+}
+export declare class BuildFederationError extends Error {
+    constructor(message: string);
+}
+/**
+ * Throws BuildFederationError if the federation build did not produce a
+ * remoteEntryPath (equivalently, buildError is set). No-op otherwise.
+ * Extracted as a standalone, pure function so the check-and-throw logic can
+ * be unit-tested directly without needing to force a real Vite failure at
+ * exactly the right pipeline stage.
+ */
+export declare function assertFederationBuildSucceeded(result: Pick<FederationBuildResult, "remoteEntryPath" | "buildError">, pluginDir: string): void;
+export interface BuildResult {
+    pluginDir: string;
+    outDir: string;
+    validation: ValidationResult;
+}
+/**
+ * Runs validate() first (Session 80) — a plugin that doesn't pass never
+ * gets packaged. On success, produces the full distributable package:
+ * remoteEntry.js + assets (a real Vite Module Federation build into the
+ * permanent outDir), server/plugin.js (a self-contained Vite SSR bundle —
+ * live functions intact, zero bare import specifiers, importable from any
+ * directory on any machine (Session 121)), and manifest.json (a redacted,
+ * JSON-safe summary for marketplace listing).
+ *
+ * Ordering note: the federation build MUST run before the server-manifest
+ * bundle, not after. buildFederationBundleTo runs Vite with
+ * `emptyOutDir: true` against the shared outDir — if bundleServerManifest
+ * had already written outDir/server/plugin.js, Vite's empty-out-dir step
+ * would delete it along with everything else in outDir before laying down
+ * remoteEntry.js. Bundling the server manifest and writing manifest.json
+ * only ever *add* files to outDir after the Vite build has already run, so
+ * neither is at risk of being clobbered by it.
+ */
+export declare function buildPlugin(pluginDir: string, outDir?: string): Promise<BuildResult>;

package/dist/build.js

@@ -0,0 +1,123 @@
+import { mkdirSync, rmSync } from "node:fs";
+import { join, resolve, sep } from "node:path";
+import { buildFederationBundleTo } from "./build-federation-bundle.js";
+import { bundleServerManifest } from "./bundle-server-manifest.js";
+import { copySampleContentIfPresent } from "./copy-sample-content.js";
+import { loadManifest } from "./load-manifest.js";
+import { packStarterIfPresent } from "./pack-starter.js";
+import { validatePlugin } from "./validate.js";
+import { writeManifestJson } from "./write-manifest-json.js";
+import { hasClientBundle } from "@velora-cms/plugin-sdk/manifest";
+export class BuildValidationError extends Error {
+    validation;
+    constructor(message, validation) {
+        super(message);
+        this.validation = validation;
+        this.name = "BuildValidationError";
+    }
+}
+export class BuildFederationError extends Error {
+    constructor(message) {
+        super(message);
+        this.name = "BuildFederationError";
+    }
+}
+/**
+ * Throws BuildFederationError if the federation build did not produce a
+ * remoteEntryPath (equivalently, buildError is set). No-op otherwise.
+ * Extracted as a standalone, pure function so the check-and-throw logic can
+ * be unit-tested directly without needing to force a real Vite failure at
+ * exactly the right pipeline stage.
+ */
+export function assertFederationBuildSucceeded(result, pluginDir) {
+    if (!result.remoteEntryPath) {
+        throw new BuildFederationError(`Vite Module Federation build failed for ${pluginDir}: ${result.buildError}`);
+    }
+}
+/**
+ * Runs validate() first (Session 80) — a plugin that doesn't pass never
+ * gets packaged. On success, produces the full distributable package:
+ * remoteEntry.js + assets (a real Vite Module Federation build into the
+ * permanent outDir), server/plugin.js (a self-contained Vite SSR bundle —
+ * live functions intact, zero bare import specifiers, importable from any
+ * directory on any machine (Session 121)), and manifest.json (a redacted,
+ * JSON-safe summary for marketplace listing).
+ *
+ * Ordering note: the federation build MUST run before the server-manifest
+ * bundle, not after. buildFederationBundleTo runs Vite with
+ * `emptyOutDir: true` against the shared outDir — if bundleServerManifest
+ * had already written outDir/server/plugin.js, Vite's empty-out-dir step
+ * would delete it along with everything else in outDir before laying down
+ * remoteEntry.js. Bundling the server manifest and writing manifest.json
+ * only ever *add* files to outDir after the Vite build has already run, so
+ * neither is at risk of being clobbered by it.
+ */
+export async function buildPlugin(pluginDir, outDir) {
+    const validation = await validatePlugin(pluginDir);
+    if (!validation.passed) {
+        throw new BuildValidationError(`validate failed for ${pluginDir} — see validation.checks for details`, validation);
+    }
+    // Resolved to absolute here (not left to buildFederationBundleTo alone)
+    // so BuildResult.outDir is always absolute and consistent for callers
+    // (CLI output, bundleServerManifest's outDir arg) regardless of whether
+    // pluginDir/outDir were passed in as relative paths.
+    const resolvedOutDir = resolve(outDir ?? join(pluginDir, "velora-package"));
+    const manifestResult = await loadManifest(pluginDir);
+    if (!manifestResult.ok) {
+        // Should be unreachable — validate() already asserts manifest validity
+        // above — but never silently package an invalid manifest if it somehow
+        // diverges (e.g. a source edit between the two loads). The `validation`
+        // object above reflects the earlier, passing validate() run, so it's
+        // spread with `passed: false` overridden here — a synthetic failed
+        // result, since the divergence discovered here never actually ran
+        // through validatePlugin()'s checks.
+        throw new BuildValidationError(`manifest became invalid between validate and build for ${pluginDir}`, {
+            ...validation,
+            passed: false,
+        });
+    }
+    if (hasClientBundle(manifestResult.manifest.type)) {
+        const federationBuild = await buildFederationBundleTo(pluginDir, resolvedOutDir);
+        assertFederationBuildSucceeded(federationBuild, pluginDir);
+    }
+    else {
+        // Client-bearing builds get this guard for free from Vite itself —
+        // it refuses an outDir that IS or CONTAINS the project root. The
+        // view-less branch below does its own recursive delete instead of
+        // calling Vite, so it needs the equivalent guard here: without it,
+        // `velora-plugin build --out .` run from inside a theme plugin's own
+        // directory resolves resolvedOutDir === pluginDir, and the rmSync
+        // below would recursively delete the plugin's own source tree before
+        // bundleServerManifest ever runs.
+        const resolvedPluginDir = resolve(pluginDir);
+        if (resolvedOutDir === resolvedPluginDir || resolvedPluginDir.startsWith(resolvedOutDir + sep)) {
+            throw new Error(`Refusing to build ${pluginDir}: outDir "${resolvedOutDir}" is the plugin's own source directory ` +
+                `(or an ancestor of it) — building here would delete the plugin's sources. Choose an outDir outside "${resolvedPluginDir}".`);
+        }
+        // The federation build is also what empties outDir (Vite's
+        // emptyOutDir) — without it a previous build's files would survive
+        // into this package. Replace-not-merge, same rule as storePackage.
+        rmSync(resolvedOutDir, { recursive: true, force: true, maxRetries: 10, retryDelay: 500 });
+        mkdirSync(resolvedOutDir, { recursive: true });
+    }
+    await bundleServerManifest(pluginDir, join(resolvedOutDir, "server"));
+    writeManifestJson(manifestResult.manifest, resolvedOutDir);
+    // S148: packs <pluginDir>/starter/ into <outDir>/starter.tar.gz when
+    // present. Runs last, same reasoning as bundleServerManifest/
+    // writeManifestJson above — it only ever *adds* a file to outDir, never
+    // at risk from (and never at risk of clobbering) the federation build's
+    // emptyOutDir step. packPlugin (pack.ts) tars the whole outDir as-is, so
+    // the archive rides inside the plugin artifact for free — no change
+    // needed there.
+    await packStarterIfPresent(pluginDir, resolvedOutDir, manifestResult.manifest);
+    // S149: copies <pluginDir>/sample-content.json into outDir when present
+    // — the seed tree a template ships (Post/Author/... sample nodes), read
+    // back host-side by apps/server/src/plugins/seed-template-content.ts
+    // AFTER install() returns (onInstall has no minted ids and no content
+    // API to create nodes with). Same legality product and same "only ever
+    // adds a file" ordering safety as packStarterIfPresent immediately
+    // above — a plain synchronous copy, never at risk from (or of
+    // clobbering) the federation build's emptyOutDir step.
+    copySampleContentIfPresent(pluginDir, resolvedOutDir, manifestResult.manifest);
+    return { pluginDir, outDir: resolvedOutDir, validation };
+}

package/dist/bundle-server-manifest.d.ts

@@ -0,0 +1,27 @@
+export declare class BundleServerManifestError extends Error {
+    constructor(message: string);
+}
+/**
+ * Bundles a plugin's manifest entry (src/plugin.ts(x) plus everything it
+ * transitively imports — INCLUDING react, react/jsx-runtime and
+ * @velora-cms/plugin-sdk) into one self-contained, Node-importable ESM file
+ * at <outDir>/plugin.js. Replaces Session 81's tsc-emit
+ * compileServerManifest: the emitted file kept bare import specifiers,
+ * which plain `import()` can only resolve by walking ancestor
+ * node_modules — true inside this monorepo, false on a real server (the
+ * S81 gap, reproduced concretely in S83 with a poisoned ancestor
+ * node_modules). A bundle resolves nothing at import time, so the same
+ * package installs anywhere.
+ *
+ * Bundling react into a SERVER-side artifact is safe by design: the
+ * server validates the manifest (Zod needs the live function references),
+ * persists it, and invokes hooks/apiRoutes handlers — it never renders
+ * views. The browser keeps loading views via remoteEntry.js with the
+ * host's Module Federation shared singletons; this file never reaches it.
+ *
+ * Deliberately configFile: false — the plugin's own vite.config.ts is
+ * the BROWSER-side federation build and must not leak in here. No
+ * process.chdir() (the buildFederationBundle concurrency caveat does not
+ * spread to this function); all paths resolved absolute up front.
+ */
+export declare function bundleServerManifest(pluginDir: string, outDir: string): Promise<string>;

package/dist/bundle-server-manifest.js

@@ -0,0 +1,93 @@
+import { existsSync, mkdirSync, writeFileSync } from "node:fs";
+import { join, resolve } from "node:path";
+import { build } from "vite";
+import { resolveManifestEntry } from "./load-manifest.js";
+export class BundleServerManifestError extends Error {
+    constructor(message) {
+        super(message);
+        this.name = "BundleServerManifestError";
+    }
+}
+/**
+ * Bundles a plugin's manifest entry (src/plugin.ts(x) plus everything it
+ * transitively imports — INCLUDING react, react/jsx-runtime and
+ * @velora-cms/plugin-sdk) into one self-contained, Node-importable ESM file
+ * at <outDir>/plugin.js. Replaces Session 81's tsc-emit
+ * compileServerManifest: the emitted file kept bare import specifiers,
+ * which plain `import()` can only resolve by walking ancestor
+ * node_modules — true inside this monorepo, false on a real server (the
+ * S81 gap, reproduced concretely in S83 with a poisoned ancestor
+ * node_modules). A bundle resolves nothing at import time, so the same
+ * package installs anywhere.
+ *
+ * Bundling react into a SERVER-side artifact is safe by design: the
+ * server validates the manifest (Zod needs the live function references),
+ * persists it, and invokes hooks/apiRoutes handlers — it never renders
+ * views. The browser keeps loading views via remoteEntry.js with the
+ * host's Module Federation shared singletons; this file never reaches it.
+ *
+ * Deliberately configFile: false — the plugin's own vite.config.ts is
+ * the BROWSER-side federation build and must not leak in here. No
+ * process.chdir() (the buildFederationBundle concurrency caveat does not
+ * spread to this function); all paths resolved absolute up front.
+ */
+export async function bundleServerManifest(pluginDir, outDir) {
+    const absolutePluginDir = resolve(pluginDir);
+    const absoluteOutDir = resolve(outDir);
+    let entryPath;
+    try {
+        entryPath = resolveManifestEntry(absolutePluginDir);
+    }
+    catch (error) {
+        throw new BundleServerManifestError(error instanceof Error ? error.message : String(error));
+    }
+    mkdirSync(absoluteOutDir, { recursive: true });
+    try {
+        await build({
+            root: absolutePluginDir,
+            configFile: false,
+            logLevel: "silent",
+            // Bundle EVERYTHING — this is the whole point. Only node: builtins
+            // stay external (also enforced via rollupOptions.external below).
+            ssr: { noExternal: true },
+            build: {
+                ssr: entryPath,
+                outDir: absoluteOutDir,
+                emptyOutDir: false,
+                // Unminified: the artifact is a server-side module a human may
+                // need to read while debugging an install, and the specifier
+                // scan in this module's tests relies on plain import syntax.
+                minify: false,
+                rollupOptions: {
+                    external: /^node:/,
+                    output: { entryFileNames: "plugin.js", format: "es", inlineDynamicImports: true },
+                },
+            },
+        });
+    }
+    catch (error) {
+        throw new BundleServerManifestError(`failed to bundle server manifest for ${absolutePluginDir}: ${error instanceof Error ? error.message : String(error)}`);
+    }
+    const bundlePath = join(absoluteOutDir, "plugin.js");
+    if (!existsSync(bundlePath)) {
+        throw new BundleServerManifestError(`bundled output missing expected entry ${bundlePath}`);
+    }
+    // Node picks a module format per file by walking UP from that file
+    // looking for the nearest package.json and reading its "type" field —
+    // ancestor directories, not just the immediate one. plugin.js itself has
+    // no extension marker (it stays "plugin.js", not "plugin.mjs" —
+    // resolveBuiltManifestPath's path is fixed), so without a package.json
+    // right here, format detection keeps walking past this outDir to
+    // whatever package.json happens to sit above wherever the package gets
+    // extracted on a real server — usually none, which makes Node default to
+    // CommonJS and fail parsing this ESM bundle with "Unexpected token
+    // 'export'". A package.json written into THIS SAME directory always
+    // wins (nearest match beats any ancestor), so the package is
+    // self-describing no matter where it's extracted. vitest's module runner
+    // (vite-node) always executes as ESM regardless of this marker, so the
+    // in-repo test suite alone can never catch its absence — only a plain
+    // Node child-process import (see bundle-server-manifest.test.ts) exposes
+    // the production failure this fixes.
+    writeFileSync(join(absoluteOutDir, "package.json"), '{"type":"module"}\n');
+    return bundlePath;
+}

package/dist/checks/audit.d.ts

@@ -0,0 +1,2 @@
+import type { CheckResult } from "../types.js";
+export declare function checkNpmAudit(pluginDir: string): CheckResult;