Repository navigation
Conversation
This was referenced Nov 16, 2026
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 05:21
b689429 to
416c8f4
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 05:55
416c8f4 to
92a5da0
Compare
allozaur
added a commit
that referenced
this pull request
Nov 17, 2026
develop now holds the fork's stack as it is after the SvelteKit 3 upgrade: the top of stack ggml-org#72 (#73, typed routes, on master with the move merged), with the side branches merged in: MCP OAuth (#63), the models manager (#38) and UI server storage (#39). The merge takes the stack's files throughout. What develop carried beyond the stack is left out for now: the mention drawer on phones (#49), the Notebook page (#57), drag-and-drop import (#56), MCP resources in the @ picker (#19), the server's ASR transcription fixes and the reasoning level shown as a word on the model selector. They were built on the stack before SvelteKit 3 and stay in their own PRs and in develop's history. Assisted-by: Claude (Opus 5.5 Medium)
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 06:43
92a5da0 to
94263f3
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 07:00
94263f3 to
1595cd4
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 10:31
1595cd4 to
76d59f1
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 11:16
76d59f1 to
e84ddbb
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
2 times, most recently
from
November 17, 2026 12:27
3f58f8a to
a225717
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
2 times, most recently
from
November 17, 2026 13:05
a17d8ea to
fdd5722
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 13:13
fdd5722 to
34d1507
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
2 times, most recently
from
November 17, 2026 13:26
2e09f9c to
b560132
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 13:44
b560132 to
d289d62
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 15:28
d289d62 to
901e6b6
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 16:26
901e6b6 to
1a1424c
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 16:42
1a1424c to
ac3f857
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
2 times, most recently
from
November 17, 2026 17:20
ed9e1b4 to
90e4f82
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 17:30
90e4f82 to
76b3bee
Compare
This was referenced Nov 17, 2026
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 22:00
76b3bee to
97a409d
Compare
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 22:21
97a409d to
4517566
Compare
ROUTES holds the app's route ids, as page.route.id reports them, in place of hash strings and the separate *_ROUTE_ID constants. Every link and goto() goes through resolve() from $app/paths, which checks the route exists and returns its URL (#/models with the hash router). RouterService resolves the routes that take params: a chat, a project, a project's chat or new chat, and an extension's page. Tab links, sidebar items and extension navigation items carry the resolved URL's type, and checks for the current page compare page.route.id instead of the hash. svelte/no-navigation-without-resolve is on again, with type information for the app's modules so a URL typed as ResolvedPathname passes. Links that leave the app say so with rel="external"; the deep-link cleanups, which change the current page's own query, are marked as such. Assisted-by: Claude (Opus 5.5 Medium)
allozaur
force-pushed
the
allozaur/refactor/ui-typed-routes
branch
from
November 17, 2026 22:35
4517566 to
fee8780
Compare
This branch has not been deployed
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
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.
Overview
Llama Chat navigates through SvelteKit 3's typed routes: every link and every
goto()names a route that TypeScript checks exists, and the lint rule that enforces it is on again. Nothing changes for the user; the URLs are the same#/…ones.Additional information
Part 10 of 13 of the work-in-progress stack on the fork, under the import costs (#74) and Pele (#75), based on
allozaur/feat/prompt-library(#29). It comes last on purpose: projects, servers, the library and the extension pages all add routes, so one pass over the finished app touches every route once, where doing it in the SvelteKit 3 layer (#70) would have conflicted with each layer that adds one.What changed
ROUTESholds route ids, aspage.route.idreports them ('/models','/(chat)/chat/[id]','/[extensionPage]', …), checked against the app's routes withsatisfies Record<string, RouteId>. The separateMODELS_ROUTE_ID,PROJECTS_ROUTE_ID,SERVERS_ROUTE_ID,SETTINGS_ROUTE_IDandEXTENSION_PAGE_ROUTE_IDconstants fold into it.goto()calls go throughresolve()from$app/paths, which returns#/modelswith the hash router.RouterServiceresolves the routes that take params: a chat, a project, a project's chat or new chat, and an extension's page.ResolvedPathname, so a raw string no longer type-checks there. The MCP extension builds its page's URL withRouterService.extensionPage().page.route.idinstead of searching the hash.svelte/no-navigation-without-resolveis on again. The app's own modules get type information in ESLint, so a value typed asResolvedPathnamepasses. Links that leave the app say so withrel="external"; the four deep-link cleanups, which change the current page's own query, carry a comment saying so.RouterServiceandresolve().Testing
ui/apps/chat:npm ci,npm run check(0 errors),npm run lint, the 1062 unit tests, the 379 client tests, the Storybook tests (115 files) andnpm run buildpass.#/library, New chat navigates to#/, the Models page opens at#/models; no console errors.resolve()only adds the#in the browser: the server build of$app/pathsreturns/models. Nothing evaluates a route at module scope on the server here, and the client tests check the#/…URLs.Requirements
Claude (Opus 5.5 Medium)