Upgrade the web application from SvelteKit 2 to SvelteKit 3.
This is a SvelteKit upgrade, not a downgrade of Svelte itself. The application currently uses Svelte 5.
Scope
Confirm the target SvelteKit 3 release and its migration requirements before implementation.
Check compatibility of Svelte, the Node adapter, Vite, authentication and other framework integrations; change related dependencies only where required.
Apply necessary migration changes while preserving current application behavior.
Validate routing, server loads/actions, authentication, SSR/hydration, CSP, theme initialization and the production Node build with the existing checks and test suites.
Out of scope
UI redesigns or new features.
Unrelated dependency upgrades or a broad application refactor.
Keep this as a focused framework migration, with any compatibility blockers investigated before coding.
## Goal
Upgrade the web application from SvelteKit 2 to SvelteKit 3.
This is a SvelteKit upgrade, not a downgrade of Svelte itself. The application currently uses Svelte 5.
## Scope
- Confirm the target SvelteKit 3 release and its migration requirements before implementation.
- Check compatibility of Svelte, the Node adapter, Vite, authentication and other framework integrations; change related dependencies only where required.
- Apply necessary migration changes while preserving current application behavior.
- Validate routing, server loads/actions, authentication, SSR/hydration, CSP, theme initialization and the production Node build with the existing checks and test suites.
## Out of scope
- UI redesigns or new features.
- Unrelated dependency upgrades or a broad application refactor.
Keep this as a focused framework migration, with any compatibility blockers investigated before coding.
This is a candidate workaround, not a verified change for When. The task remains blocked pending supported compatibility or an explicit decision to adopt a workaround.
Possible interim solution to evaluate while waiting for an upstream Auth.js update: https://github.com/nextauthjs/next-auth/discussions/13503
This is a candidate workaround, not a verified change for When. The task remains blocked pending supported compatibility or an explicit decision to adopt a workaround.
The authentication compatibility blocker is addressed by merged PR #106: #106 (commit 7802f13). Auth.js has been replaced with stateless Better Auth.
The application remains on SvelteKit 2; the SvelteKit 3 migration described in this issue is still outstanding, so this issue remains open.
The authentication compatibility blocker is addressed by merged PR #106: https://git.eleith.com/eleith/when/pulls/106 (commit `7802f13`). Auth.js has been replaced with stateless Better Auth.
The application remains on SvelteKit 2; the SvelteKit 3 migration described in this issue is still outstanding, so this issue remains open.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Upgrade the web application from SvelteKit 2 to SvelteKit 3.
This is a SvelteKit upgrade, not a downgrade of Svelte itself. The application currently uses Svelte 5.
Scope
Out of scope
Keep this as a focused framework migration, with any compatibility blockers investigated before coding.
upgrade to svelte 3to Upgrade to SvelteKit 3Blocked on Auth.js compatibility with SvelteKit 3. Revisit when @auth/sveltekit supports the target SvelteKit 3 release.
Possible interim solution to evaluate while waiting for an upstream Auth.js update: https://github.com/nextauthjs/next-auth/discussions/13503
This is a candidate workaround, not a verified change for When. The task remains blocked pending supported compatibility or an explicit decision to adopt a workaround.
The authentication compatibility blocker is addressed by merged PR #106: #106 (commit
7802f13). Auth.js has been replaced with stateless Better Auth.The application remains on SvelteKit 2; the SvelteKit 3 migration described in this issue is still outstanding, so this issue remains open.