@dxos/app-framework 0.8.4-main.fffef41 → 0.9.0

package/dist/types/src/vite-plugin/manifest.d.ts

@@ -0,0 +1,41 @@
+import { type Plugin } from '../core';
+/**
+ * Name of the asset written alongside the built module bundle.
+ * The DXOS community registry resolves each published plugin by fetching this file
+ * from the repo's latest GitHub Release, so authors should not rename it.
+ */
+export declare const MANIFEST_ASSET_NAME = "manifest.json";
+/**
+ * Canonical entry filename (re-exported from `@dxos/protocols`) so vite-plugin
+ * consumers don't have to reach into the protocols package directly.
+ */
+export declare const ENTRY_FILENAME = "index.mjs";
+/**
+ * Plugin metadata required to emit a manifest at build time.
+ *
+ * Extends `Plugin.Meta` with a build-time `version` field that is not
+ * relevant to the runtime plugin definition itself.
+ */
+export type BuildMeta = Plugin.Meta & {
+    version: string;
+};
+/**
+ * Serializes a plugin's public metadata + bundle layout into the format consumed
+ * by the host loader (see `UrlLoader.make` and `PluginManifest.parse`).
+ *
+ * The host fetches this manifest, resolves every entry in `assets` against the
+ * manifest URL, and persists them via the platform `PluginAssetCache` so the
+ * plugin works offline. For production builds the entry module is always
+ * {@link ENTRY_FILENAME} and must appear in `assets`. For dev-server manifests
+ * pass `devEntry` (a path relative to the manifest URL) — the host then imports
+ * the entry directly from the dev server and skips offline caching, since the
+ * full asset graph isn't enumerable until build time.
+ *
+ * Exported from a vite-free module so tests and tooling can validate manifests
+ * without paying the cost of loading vite + esbuild.
+ */
+export declare const serializeManifest: (meta: BuildMeta, { assets, devEntry }: {
+    assets: readonly string[];
+    devEntry?: string;
+}) => string;
+//# sourceMappingURL=manifest.d.ts.map

package/dist/types/src/vite-plugin/manifest.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.d.ts","sourceRoot":"","sources":["../../../../src/vite-plugin/manifest.ts"],"names":[],"mappings":"AAMA,OAAO,EAAE,KAAK,MAAM,EAAE,MAAM,SAAS,CAAC;AAEtC;;;;GAIG;AACH,eAAO,MAAM,mBAAmB,kBAAkB,CAAC;AAEnD;;;GAGG;AACH,eAAO,MAAM,cAAc,cAAwB,CAAC;AAEpD;;;;;GAKG;AACH,MAAM,MAAM,SAAS,GAAG,MAAM,CAAC,IAAI,GAAG;IAAE,OAAO,EAAE,MAAM,CAAA;CAAE,CAAC;AAE1D;;;;;;;;;;;;;;GAcG;AACH,eAAO,MAAM,iBAAiB,SACtB,SAAS,wBACO;IAAE,MAAM,EAAE,SAAS,MAAM,EAAE,CAAC;IAAC,QAAQ,CAAC,EAAE,MAAM,CAAA;CAAE,KACrE,MAeF,CAAC"}

package/dist/types/src/vite-plugin/manifest.test.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=manifest.test.d.ts.map

package/dist/types/src/vite-plugin/manifest.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"manifest.test.d.ts","sourceRoot":"","sources":["../../../../src/vite-plugin/manifest.test.ts"],"names":[],"mappings":""}

package/dist/types/src/vite-plugin/packages.d.ts

@@ -0,0 +1,13 @@
+export declare const DEFAULT_PACKAGES: string[];
+/**
+ * True when the given bare specifier (or one of its subpaths) is provided by the
+ * Composer host at runtime and must not be re-bundled by a plugin.
+ *
+ * Matches only packages listed in {@link DEFAULT_PACKAGES} — the same list
+ * {@link importMapPlugin} consumes — so externalization cannot claim a package
+ * the host isn't actually mapping. Unknown `@dxos/*` packages fall through to
+ * normal bundling, which is the correct default for plugin-owned or yet-to-be
+ * shared workspace packages.
+ */
+export declare const isSharedPackage: (id: string) => boolean;
+//# sourceMappingURL=packages.d.ts.map

package/dist/types/src/vite-plugin/packages.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"packages.d.ts","sourceRoot":"","sources":["../../../../src/vite-plugin/packages.ts"],"names":[],"mappings":"AAyCA,eAAO,MAAM,gBAAgB,UAoI5B,CAAC;AAEF;;;;;;;;;GASG;AACH,eAAO,MAAM,eAAe,OAAQ,MAAM,KAAG,OAC2B,CAAC"}