Refactor pages into Rabbita incremental components - #173
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 page-wide message forwarding with Rabbita incremental components for routing, docs, home, Skills, profiles, and the build queue. The entry points own
@rabbita.new; page components exposeVal[Html].Docs retain the current module manifest, index, and sidebar when switching packages in that module. Package content changes independently. Keep the local manifest reuse workaround documented until Rabbita can support the required reactive routing behavior. Theme rendering follows model state, and the Skills showcase timer continues after asynchronous loading.
Development now defaults
VITE_SKILLS_HOSTtoskills.mooncakes.io; production builds still require it explicitly. Upgrade Rabbita to 0.15.4 and remove obsolete helpers and status adapters.Validation: 61 existing tests pass for JS debug/release, native, and Wasm; all three targets pass
--deny-warn; formatting, generated interfaces, typos, Vite production build, and native SSR build pass. Temporary browser checks cover SSR/hydration, docs navigation and component reuse, anchors, search, theme, Skills, downloads, profiles, and build queue in Chromium desktop/mobile and Firefox. No new test files are included. Safari/WebKit could not launch locally.Known existing limitation: an HTTP 404 during SSR uses Rabbita’s fallback behavior, so the skeleton becomes an error after browser hydration. This also occurs with the previous Rabbita version.
Deployment requires the companion frontend_service entry-point and dependency update in the parent repository.