-
Notifications
You must be signed in to change notification settings - Fork 1
feat: add frontend-sveltekit module #5
Copy link
Copy link
Open
Labels
good first issueGood for newcomersGood for newcomersmodule: frontendRelated to frontend frameworks, UI libraries, or client-side architecture.Related to frontend frameworks, UI libraries, or client-side architecture.new-modulebuild something herebuild something here
Metadata
Metadata
Assignees
Labels
good first issueGood for newcomersGood for newcomersmodule: frontendRelated to frontend frameworks, UI libraries, or client-side architecture.Related to frontend frameworks, UI libraries, or client-side architecture.new-modulebuild something herebuild something here
Summary
Add SvelteKit as a frontend option in the
foundation createinteractive prompt, alongside the existingfrontend-sveltemodule.Why
SvelteKit is the production framework for Svelte projects (routing, SSR, adapters) — analogous to how Next.js relates to React.
The current
frontend-sveltemodule generates a plain Vite + Svelte app, which stops short of what most developers actually want.Files to generate
src/routes/+page.svelte— root page componentsrc/routes/+layout.svelte— root layoutsvelte.config.js— with@sveltejs/adapter-autovite.config.tstsconfig.json.env.exampleImplementation hints
Add
packages/modules/src/frontend/sveltekit.ts→ copy
svelte.tsas the starting point, swap the files array and package depsRegister in:
index.tsregistry-loader.tsgraph-definition.tsunder
frontendchoicesKey dependencies:
@sveltejs/kit@sveltejs/adapter-autosvelteviteConflicts with:
frontend-svelte(same category)Contributor guidance
To better understand the implementation flow and module system, refer to:
➡️ CONTRIBUTING.md — especially the section on adding a new module
Acceptance criteria
foundation createlists SvelteKit as a frontend optionvite devwithout errorstsconfig.jsonincludes.svelte-kit/tsconfig.jsonextendpackages/modules