· developers · examples
Every example is a
create-vesk
template —
npm install && npm run dev
and it works. No glue, no extra config.
File routing ([slug], [...rest]), layouts, loading/error. Compare: Next app/ is similar, Vesk adds manual routing & hash.
useFetch with into cells, staleTime, HttpError. Compare: Next fetch caching is implicit, Vesk is explicit.
Form + Field + defineAction + Zod. Compare: Remix actions are per-route, Vesk actions are per-component.
This site — full-text derived search, <10 ms. Compare: Next docs often need Algolia.
Same UI on web + Kotlin. Compare: Expo requires separate app, Flutter Dart rewrite.
<Md content>, code copy, GFM, HTML policy. Compare: Astro MD is build-only, Vesk streams live.
| Primitive | Vesk lines | Next / SvelteKit |
|---|---|---|
| Counter (state + effect) | 3 — let &[c]=track(0) | ~7 — useState + useEffect |
| Data load + SSR | 1 — useFetch('/api/posts') | 4-8 — fetch + loader/getServerSideProps |
| Form validation | 3 — Form + Field + defineAction | ~15-20 — RHF/Zod + handler |
| Zero-JS page | 0 — just markup, compiler proves | — always ships runtime |
Fewer lines, fewer runtime concepts, less to debug — the compiler carries the weight.