refactor: modernize the Svelte frontend with Vite - #79
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace the legacy Rollup pipeline with Vite and the official Svelte plugin, using native Svelte TypeScript support. Update frontend tooling and compatible dependency resolutions, remove obsolete dependencies, and standardize Node 24 and Yarn 4.18.
Keep CodeMirror and Dygraphs instances alive when changing fullscreen or data. Adapt the AppImage smoke test to verify actual styles and instance preservation. Resolve benchmark assets from each revision's Tauri configuration and prepare frontend assets for Rust CodeQL extraction.
Validation: type checking, lint, production build and seven benchmark detector tests pass. The recursive npm audit reports no vulnerabilities. CI verifies four desktop targets, packaged Linux interactions, performance and CodeQL. The release plan remains uncommitted.