SAsamuelstros·Dec 14, 2023
Glad that inlang could contribute i18n routing capabilities for SvelteKit 2.0!
https://inlang.com/c/svelte and https://github.com/sveltejs/kit/pull/10755
In SvelteKit 2sveltejs
kit
JavaScript2021–2026
sveltejs / kit
kit
web development, streamlined
25Distinct people
31Mentions
0Explicit recommenders
20.9KGitHub stars
What to know before exploring
What it is
web development, streamlined
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- brillout/vite-plugin-ssr · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year31 dated mentions
Observed mentions: 2021-03-11 23:50:14 UTC to 2026-10-01 19:42:44 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 7 | 2 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 8 | 3 | 5 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 2 | 2 | 0 |
What Hacker News says
5 sourcesI just started a project and chose this stack:
- SSR SvelteKit with Hydration (https://github.com/sveltejs/kit)
- PostgreSQL database server
- Postgres.js - PostgreSQL client for Node.js (https://github.com/porsager/postgres)
- Migration powered by graphile-migrate (https://github.com/graphile/migrate)
- PostgreSQL Row-Level Security (https://www.postgresql.org/docs/16/ddl-rowsecurity.html)
- svelte-headlessui (https://github.com/rgossiaux/svelte-headlessui)
- sveltekit-i18n (https://github.com/sveltekit-i18n/lib)
- TailwindCSS (https://tailwindcss.com/)
- Superforms (https://superforms.rocks/)
- sveltekit-flash-message + svelte-french-toast (https://github.com/ciscoheat/sveltekit-flash-message + https://github.com/kbrgl/svelte-french-toast)
Tooling :
- asdf (https://asdf-vm.com/)
- Docker and Docker Compose
- NodeJS
- pnpm
- Jest for uni
Read the rest
ttest
All deployed on a VM at Scaleway (https://www.scaleway.com/en/) with Bash script (https://github.com/stephane-klein/sveltekit-tendaro-webshell...)
After 3 months of development on this stack, I'm very satisfied. My application is fast, light and requires very little code.
Project skeleton example: https://github.com/stephane-klein/sveltekit-tendaro-webshell...
FYI SvelteKit moved from file-based routing to filesystem-based or directory-based routing[1]. This change was inspired by next.js[2]
Many users grumbled about needing more folders and files. With many files sharing the same name. But I think this was the right choice. See the explanations in the links below.
[1]: https://github.com/sveltejs/kit/discussions/5037
[2]: https://nextjs.org/blog/layouts-rfc
In Show HN: Node.js File-based routing back end libraryAs far as I'm aware, SvelteKit has fully supported Deno since 1.17.0: https://github.com/sveltejs/kit/blob/master/packages/kit/CHA...
In Svelte 4Svelte creator and Vercel employee here. Vercel does indeed invest heavily in Svelte and SvelteKit, not least by employing me and Simon Holthausen (and potentially others in future), but there's no danger of lock-in — we're just two members of a much larger core team. Governance-wise, it's an independent project, and we'd be thrilled if other companies also chose to employ core team members! You can see pull requests like https://github.com/sveltejs/kit/pull/8740 as an example of how we approach the relationship between SvelteKit and Vercel — we're adding a new feature and Vercel will be the first adapter that gets to take advantage of it, but we're careful to design the feature in a platform-agnostic way (we even @'d a Netlify engineer to make sure that they're aware of the work in case they also want to take advantage of it).
Anyway, I'
Read the rest
m sure this will be said elsewhere in the thread but it bears repeating — the Next team similarly works hard to make sure that your Next apps can be self-hosted and run on other platforms.