Our development team has been using Svelte 5.0 as the frontend framework so far. There were several reasons for this, but primarily it was chosen out of curiosity from the project maintainer and a desire to experiment with newer technologies.
However, due to Svelte 5.0's (subjectively) complex Rune syntax and relatively limited ecosystem, we experienced difficulties during development. Currently, only one person on the team can work with Svelte, and even that experience is not at an expert level.
In particular, the challenges and complexity encountered during the refactoring process in PR #27 reached a point where we believe future maintenance and handover would become very difficult.
After discussion, we decided to move away from Svelte and transition to React and Next.js (with SSR support) to address these issues. Although these frameworks may be somewhat heavier than Svelte, we concluded that, given the nature of this project, the trade-off is worthwhile in favor of stability and maintainability.
The migration from Svelte to Next.js will begin on February 13, 2026. Previously, both backend and frontend source code were managed in a single monorepo for development convenience. However, as the project grows, we believe the monorepo approach is becoming a disadvantage.
Therefore, we will separate the frontend into its own repository, and the existing Svelte frontend source code will be marked as deprecated. It will also be archived in a separate repository.
Our development team has been using Svelte 5.0 as the frontend framework so far. There were several reasons for this, but primarily it was chosen out of curiosity from the project maintainer and a desire to experiment with newer technologies.
However, due to Svelte 5.0's (subjectively) complex Rune syntax and relatively limited ecosystem, we experienced difficulties during development. Currently, only one person on the team can work with Svelte, and even that experience is not at an expert level.
In particular, the challenges and complexity encountered during the refactoring process in PR #27 reached a point where we believe future maintenance and handover would become very difficult.
After discussion, we decided to move away from Svelte and transition to React and Next.js (with SSR support) to address these issues. Although these frameworks may be somewhat heavier than Svelte, we concluded that, given the nature of this project, the trade-off is worthwhile in favor of stability and maintainability.
The migration from Svelte to Next.js will begin on February 13, 2026. Previously, both backend and frontend source code were managed in a single monorepo for development convenience. However, as the project grows, we believe the monorepo approach is becoming a disadvantage.
Therefore, we will separate the frontend into its own repository, and the existing Svelte frontend source code will be marked as deprecated. It will also be archived in a separate repository.
Ultimately, we decided not to adopt Next.js and instead migrate to plain React.
Next.js and its SSR capabilities are considered too heavy for our project’s needs. Since CSR is sufficient and SEO is not a concern, we chose this approach. Next.js will not be adopted.