fix release build blank screen

Author: passpier

.github/workflows/release.yml

@@ -85,7 +85,6 @@ jobs:
             - PDF import handles text-based PDFs only — no scanned/OCR; complex multi-column layouts may reorder.
             - Spreadsheet import is capped at 500 rows/sheet; images can't be mapped to a specific cell.
             - Vector images (EMF/WMF) can't be displayed; pptx animations are dropped.
-            - **Builds are unsigned / un-notarized.** On macOS you must remove the quarantine flag (`xattr -dr com.apple.quarantine "/Applications/Pourdown.app"`); on Windows, SmartScreen may need a one-time "More info → Run anyway". See the README for step-by-step install instructions.
           releaseDraft: true
           prerelease: true
           args: ${{ matrix.args }}

vite.config.ts

@@ -52,24 +52,17 @@ export default defineConfig(async () => ({
     },
     rollupOptions: {
       output: {
-        manualChunks: {
-          // mermaid is already dynamically imported per-block; this gives it a stable chunk name
-          mermaid: ["mermaid"],
-          tiptap: [
-            "@tiptap/core",
-            "@tiptap/react",
-            "@tiptap/starter-kit",
-            "@tiptap/extension-image",
-            "@tiptap/extension-placeholder",
-            "@tiptap/extension-table",
-            "@tiptap/extension-table-cell",
-            "@tiptap/extension-table-header",
-            "@tiptap/extension-table-row",
-            "@tiptap/extension-typography",
-          ],
-          lowlight: ["lowlight", "@tiptap/extension-code-block-lowlight"],
-          i18n: ["i18next", "react-i18next"],
-        },
+        // No manualChunks: a prior grouping (mermaid/tiptap/lowlight/i18n
+        // into fixed chunks) produced a `ReferenceError: Cannot access
+        // uninitialized variable` at module-eval time in built bundles
+        // (both debug and release `tauri build`, never in `tauri dev` since
+        // the dev server doesn't bundle) — a classic manualChunks
+        // circular/init-order TDZ bug, most likely from splitting
+        // `react-i18next` away from the `react` chunk it depends on at
+        // eval time. Letting rollup auto-split by the import graph
+        // guarantees correct init order at the cost of slightly less
+        // predictable chunk names, which doesn't matter for a desktop app
+        // serving local assets.
       },
     },
   },