@rsc-kit/core 0.9.0 → 0.11.0

package/dist/vite.d.ts

@@ -1,3 +1,4 @@
+import type { WebManifestOptions } from './webManifest.js';
 import type { PluginOption } from 'vite';
 export interface RscKitOptions {
     /** Project root. Defaults to RSC_PROJECT_ROOT, then cwd. */
@@ -188,5 +189,37 @@ export interface RscKitOptions {
  * Nothing else is touched. An action is a POST and must never be answered from
  * a cache; anything cross-origin is somebody else's to cache.
  */
-export declare const SERVICE_WORKER: (version: string, precache: string[]) => string;
+export declare const SERVICE_WORKER: (version: string, precache: string[], frozen?: string[]) => string;
+/**
+ * Write the worker beside the assets it caches.
+ *
+ * The version is a hash of what is being precached rather than a build id from
+ * the environment. The names are content-hashed already, so a build that
+ * changed nothing produces the same list and leaves the visitor's cache alone,
+ * and a build that changed anything produces a different one — which is the
+ * whole of cache invalidation, without asking anyone to set a variable.
+ */
+/**
+ * Write the web app manifest into the client output, beside the assets.
+ *
+ * Into the same directory the browser is served from, because that is where a
+ * relative icon path resolves — a manifest served from somewhere else resolves
+ * its icons somewhere else too, and the failure is a browser that quietly does
+ * not offer to install.
+ */
+/**
+ * The manifest an app declared beside its routes.
+ *
+ * `src/app/manifest.ts`, default-exporting the object — the same shape every
+ * other thing about a route tree takes here, and the reason this is a file
+ * rather than a `vite.config.ts` key. A manifest is not build configuration
+ * any more than a page is; it is one more thing the app declares about itself,
+ * and it belongs where the app is.
+ *
+ * Evaluated with the TypeScript stripped rather than imported: this runs while
+ * the plugin is being constructed, long before there is a module graph to pull
+ * it through, and importing an app module here would drag its imports in with
+ * it. The file is a literal object by contract, which is all that has to parse.
+ */
+export declare function declaredManifest(appDir: string): WebManifestOptions | null;
 export declare function rscKit(options?: RscKitOptions): PluginOption[];