Our great sponsors
-
Exciting to see this hit 1.0! The new tutorial site looks great and I love that the sidebar is searchable now. Also the Cmd-K search on the docs (https://kit.svelte.dev/) is awesome to have as well.
I've been really enjoying working with Svelte for the last year or so now. My main project is a video editor, running under Tauri, but I've also used SvelteKit to throw together a few little admin dashboard-y things and it's been very quick to get started with. Right now those projects are pretty lightweight too, just SvelteKit with TypeScript, the pg-promise package to connect with Postgres, and a handful of handwritten SQL queries.
Congrats to the team! Looking forward to see what the future holds for Svelte[Kit].
-
swyxkit
An opinionated blog starter for SvelteKit + Tailwind + Netlify. Refreshed for SvelteKit 1.0!
congrats team!
the livestream and meta discussions around the launch are happening here https://www.youtube.com/watch?v=N4BRVkQVoMc
I've been keeping a reference implementation of a SvelteKit blog, inspired by @leerob's nextjs site: https://github.com/sw-yx/swyxkit/ for the past year and it's now updated for 1.0
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
If you're just learning SvelteKit, check this tool out: https://github.com/svelte-add/svelte-add
It will save you a ton of time by making it really easy to add integrations to your projects (like Tailwind, Bootstrap, Supabase, Jest, etc)
-
budibase
Budibase is an open-source low code platform that helps you build internal tools in minutes 🚀
budibase is a notable interface builder in Svelte if anyone wants to compare https://github.com/Budibase/budibase
and ofc huggingface gradio counts too https://www.svelteradio.com/episodes/gradio-with-pngwn
-
While I like Svelte, I fear it looses some of the flexible API-building enabled by React.
Specifically, since it uses a template system, you can't pass around interface definitions as easily.
- https://github.com/sveltejs/svelte/issues/3480 (no dynamic slots)
-
Requests are routed reverse proxy (Caddy) -> Vite (SSR) -> Python (Pyramid).
SSR calls your backend APIs and renders templates.
Example from SvelteKit page.ts here:
https://github.com/tradingstrategy-ai/frontend/blob/master/s...
Some remarks
- page.ts is routed by Vite for every HTTP request for SSR and then it will fetch() data over backend API
- If rendered in the client, fetch() hits directly the backend API
- Both cases the template is rendered using the same logic (Svelte HTML templating, CSS, JS)
- You are going to need a template language any cases, like Django's one. Alternative way to think this is that SvelteKit is just a super powerful template engine.
-
It's worse than that, sadly. A lot of what is perceived as standards (that is they have an official sounding spec on w3c somewhere) are actually not, and are just Chrome releasing stuff.
If you go to MDN and click on multiple experimental APIs you'll find they do have a spec. And they are shipped in Chrome. And then you start reading the spec and it says "It is not a W3C Standard nor is it on the W3C Standards Track.": https://developer.mozilla.org/en-US/docs/Web/API
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
