-
fix: remove paraglideVitePlugin from vite.config — root cause of 500 errors
Some checks failedCI / Backend (push) Failing after 11sCI / UI (push) Successful in 45sRelease / Test backend (push) Successful in 53sRelease / Check ui (push) Successful in 1m3sRelease / Docker / caddy (push) Successful in 55sCI / Backend (pull_request) Successful in 48sRelease / Docker / backend (push) Failing after 11sRelease / Docker / runner (push) Failing after 11sCI / UI (pull_request) Successful in 50sRelease / Docker / ui (push) Successful in 2m20sRelease / Gitea Release (push) Has been skippedreleased 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:- Overwrites messages.js with 'export * as m from ...' unconditionally
- Causes Rollup SSR tree-shaking to replace all m.*() calls with (void 0)
- 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