@despia/local 1.0.6 → 1.0.8

package/README.md

@@ -4,7 +4,7 @@ Universal build plugin to generate `despia/local.json` manifest for [Despia](htt
 
 **Note**: Despia's local server is optional. Normally, the Despia runtime can run your web app directly from a URL. Despia's local server is for developers who need extra performance and full true native offline support.
 
-**Store Compliant**: Despia's local server is fully compliant with Apple App Store and Google Play Store guidelines. It downloads and caches web content (HTML, CSS, JavaScript) for offline display in a WebView—identical to how web browsers work. No native code or executables are downloaded. See [Store Compliance & Security](#store-compliance--security) section for detailed compliance information.
+**Store Compliant**: Despia's local server is fully compliant with Apple App Store and Google Play Store guidelines. It downloads and caches web content (HTML, CSS, JavaScript) for offline display in a WebView - identical to how web browsers work. No native code or executables are downloaded. See [Store Compliance & Security](#store-compliance--security) section for detailed compliance information.
 
 ## Features
 
@@ -155,7 +155,7 @@ Despia's local server complies with this guideline because:
    - Binary behavior
    - System integration
 
-   **However**, the web UI can be updated to use existing native APIs in new ways. For example, if Face ID is already implemented in the native code and exposed through the WebView bridge, the web UI can be updated to call Face ID from new parts of the app. This is compliant because the native capability already exists in the submitted binary—only the web UI's usage of it changes.
+   **However**, the web UI can be updated to use existing native APIs in new ways. For example, if Face ID is already implemented in the native code and exposed through the WebView bridge, the web UI can be updated to call Face ID from new parts of the app. This is compliant because the native capability already exists in the submitted binary - only the web UI's usage of it changes.
 
    **Note**: This follows the same pattern as [Expo](https://expo.dev), which has been generally accepted by app stores. However, Apple's interpretation of "feature changes" under Guideline 3.3.2 is subjective, and your app could still face review challenges. It's recommended to be conservative with updates that significantly change app behavior, even when using existing native APIs.
 
@@ -183,7 +183,7 @@ Despia's local server complies with this policy because:
 
 4. **Sandboxed Execution**: All web content executes within the WebView's security sandbox, with permissions and capabilities fixed at APK submission time.
 
-   **However**, the web UI can be updated to use existing native APIs in new ways. For example, if biometric authentication is already implemented in the native code and exposed through the WebView bridge, the web UI can be updated to call it from new parts of the app. This is compliant because the native capability already exists in the submitted APK—only the web UI's usage of it changes.
+   **However**, the web UI can be updated to use existing native APIs in new ways. For example, if biometric authentication is already implemented in the native code and exposed through the WebView bridge, the web UI can be updated to call it from new parts of the app. This is compliant because the native capability already exists in the submitted APK - only the web UI's usage of it changes.
 
 **This approach is explicitly permitted** under Play Store policies, as evidenced by:
 - Chrome and other browsers rendering web content
@@ -649,6 +649,7 @@ The generated `despia/local.json` file contains an object with the entry HTML pa
 {
   "entry": "/index.html",
   "assets": [
+    "/index.html",
     "/assets/app.abc123.css",
     "/assets/app.def456.js",
     "/assets/logo.xyz789.png"
@@ -656,8 +657,8 @@ The generated `despia/local.json` file contains an object with the entry HTML pa
 }
 ```
 
-- **`entry`**: The entry HTML file path (e.g., `/index.html`). **Required** - Local apps always need an entry point for client-side rendering. When `skipEntryHtml` is enabled, the entry is still required in the manifest but won't be included in the `assets` array.
-- **`assets`**: A sorted array of all asset paths (excluding the entry file).
+- **`entry`**: The entry HTML file path (e.g., `/index.html`). **Required** - Local apps always need an entry point for client-side rendering. The entry path is also included in the `assets` array (unless `skipEntryHtml` is enabled).
+- **`assets`**: A sorted array of all asset paths, **including the entry file**. When `skipEntryHtml` is enabled, the entry is still required in the manifest but won't be included in the `assets` array.
 
 ## Examples
 
@@ -748,7 +749,7 @@ export default defineConfig({
 2. **Scan Output Directory** - Recursively scans the build output directory for all files
 3. **Collect Asset Paths** - Collects paths from both the build tool's bundle metadata and file system
 4. **Normalize Paths** - Converts all paths to root-relative format (starting with `/`)
-5. **Separate Entry from Assets** - Identifies the entry HTML file and separates it from other assets
+5. **Include Entry in Assets** - Identifies the entry HTML file and includes it in the assets array (unless `skipEntryHtml` is enabled)
 6. **Sort & Write** - Sorts asset paths alphabetically and writes object format `{ entry, assets }` to `despia/local.json`
 
 The generated manifest is then used by Despia during app hydration and updates to ensure all assets are properly cached for offline operation.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@despia/local",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "description": "Universal build plugin to generate despia/local.json manifest for offline caching in Despia web-native apps. Supports Vite, Webpack, Rollup, Nuxt, SvelteKit, Astro, Remix, esbuild, Parcel, and more.",
   "type": "module",
   "main": "./src/core.js",