The plugin hooks into your build tool’s completion event, scans the output directory, and generates the manifest at despia/local.json.
The manifest must always be served at despia/local.json relative to your web app’s root. Do not change this path. Despia expects it at this exact location to detect and apply updates.
The entry HTML file path. Always required for client-side rendering.
deployed_at
Timestamp in milliseconds (as string) when the manifest was generated. Updated on every deployment and used by the OTA cache system to detect new builds.
assets
Alphabetically sorted array of all asset paths, including the entry file.
This manifest enables Despia to discover all assets for complete caching, determine changes via deployed_at, guarantee offline operation, and perform atomic updates safely.
For apps that need to maintain compatibility across different runtime versions, use despia-version-guard to conditionally render features based on the installed native runtime version.
import { VersionGuard } from 'despia-version-guard';// Only renders this feature if the runtime version is 21.0.3 or higher<VersionGuard min_version="21.0.3"> <NewFeatureComponent /></VersionGuard>
Use case
Why it helps
Store compliance
Version-gate major UI changes to satisfy review requirements
Prevent broken UI
Ensure features only render when the required runtime capability is available
Smooth rollouts
Gradually introduce new capabilities without forcing immediate updates
Enterprise stability
Maintain consistent behavior across deployments with mixed runtime versions
despia-version-guard supports React, Vue, Angular, Svelte, and Vanilla JS / Web Components.