• fix: remove paraglideVitePlugin from vite.config — root cause of 500 errors
    Some checks failed
    CI / Backend (push) Failing after 11s
    CI / UI (push) Successful in 45s
    Release / Test backend (push) Successful in 53s
    Release / Check ui (push) Successful in 1m3s
    Release / Docker / caddy (push) Successful in 55s
    CI / Backend (pull_request) Successful in 48s
    Release / Docker / backend (push) Failing after 11s
    Release / Docker / runner (push) Failing after 11s
    CI / UI (pull_request) Successful in 50s
    Release / Docker / ui (push) Successful in 2m20s
    Release / Gitea Release (push) Has been skipped

    kamil released this 2026-03-30 23:15:27 +05:00

    The paraglideVitePlugin runs at build time (buildStart hook) and fetches
    the inlang plugin from cdn.jsdelivr.net to recompile messages. This:

    1. Overwrites messages.js with 'export * as m from ...' unconditionally
    2. Causes Rollup SSR tree-shaking to replace all m.*() calls with (void 0)
    3. Crashes every page server-side with 'TypeError: (void 0) is not a function'

    The plugin is no longer needed: compiled paraglide output is committed to
    git and updated via 'npm run paraglide' when messages change. Removing the
    plugin lets Vite treat messages.js as a plain static module, keeping all
    exports intact through the SSR bundle.

    Downloads