sveltejs

svelte

JavaScript2017–2026

sveltejs / svelte

svelte

web development for the rest of us

Web Development Languages & Compilers

Explore on GitHub Read Hacker News discussions

74Distinct people

93Mentions

4Explicit recommenders

88.8KGitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

web development for the rest of us

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I love Svelte, but you are absolutely right about Solid's influence. Svelte's Signals implementation seems very performant compared to other Signals-based frameworks. [0] [0]…

division_by_0 used a recommendation phrase. 4 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

solidjs/solid · 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, 9:01:12 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 year93 dated mentions

Observed mentions: 2017-01-08 02:15:41 UTC to 2026-06-14 17:35:58 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

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Submissions	Comments
2017	2017-01-01 00:00:00 UTC	2018-01-01 00:00:00 UTC	1	0	1
2018	2018-01-01 00:00:00 UTC	2019-01-01 00:00:00 UTC	3	0	3
2019	2019-01-01 00:00:00 UTC	2020-01-01 00:00:00 UTC	20	2	18
2020	2020-01-01 00:00:00 UTC	2021-01-01 00:00:00 UTC	8	0	8
2021	2021-01-01 00:00:00 UTC	2022-01-01 00:00:00 UTC	3	1	2
2022	2022-01-01 00:00:00 UTC	2023-01-01 00:00:00 UTC	11	0	11
2023	2023-01-01 00:00:00 UTC	2024-01-01 00:00:00 UTC	12	4	8
2024	2024-01-01 00:00:00 UTC	2025-01-01 00:00:00 UTC	12	9	3
2025	2025-01-01 00:00:00 UTC	2026-01-01 00:00:00 UTC	20	2	18
2026 (partial)	2026-01-01 00:00:00 UTC	2027-01-01 00:00:00 UTC	3	0	3

What Hacker News says

12 sources

Raed667·Aug 8, 2023

I don't want to dismiss Svelete entierly but this code `<button on:click={handleClick}>` smells like old bad ideas instead of fresh air. It is yet another custom templating language with its unique limits [0]. If I have an option i'll stick with JSX. [0] https://github.com/sveltejs/svelte/issues/5112#

In Svelte 5 is going to be radical

mtmail·Jul 23, 2023

(From https://github.com/sveltejs/svelte/issues/6629#issuecomment-...) "The reason why autofocus should be generally avoided, is that it's messing up the focus order for screenreaders and similar assistive technologies. Additionally, logical "focus order" is also a success criterion on the official WCAG 2.0 accessibility guidelines by the W3C." https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechan...

In Ask HN: Why do web sites not place the cursor for input?

swyx·Jun 22, 2023

read TFA: > "Svelte 3 was released more than four years ago... Svelte 4 is mainly a maintenance release, bumping minimum version requirements and tightening up the design in specific areas." Major Changes breaking: Minimum supported Node version is now Node 16 (#8566) breaking: Minimum supported webpack version is now webpack 5 (#8515) breaking: Bundlers must specify the browser condition when building a frontend bundle for the browser (#8516) breaking: Minimum supported vite-plugin-svelte version is now 2.4.1. SvelteKit users can upgrade to 1.20.0 or newer to ensure a compatible version ([#8516] (#8516)) breaking: Minimum supported rollup-plugin-svelte version is now 7.1.5 (198dbcf) breaking: Minimum supported svelte-loader is now 3.1.8 (198dbcf) breaking: Minimum supported TypeScript version is now TypeScript 5 (it will likely work with

Read the rest

lower versions, but we make no guarantees about that) ([#8488] (#8488)) breaking: Remove svelte/register hook, CJS runtime version and CJS compiler output (#8613) breaking: Stricter types for createEventDispatcher (see PR for migration instructions) (#7224) breaking: Stricter types for Action and ActionReturn (see PR for migration instructions) (#7442) breaking: Stricter types for onMount - now throws a type error when returning a function asynchronously to catch potential mistakes around callback functions (see PR for migration instructions) (#8136) breaking: Overhaul and drastically improve creating custom elements with Svelte (see PR for list of changes and migration instructions) ([#8457](https://github. com//pull/8457)) breaking: Deprecate SvelteComponentTyped in favor of SvelteComponent (#8512) breaking: Make transitions local by default to prevent confusion around page navigations (#6686) breaking: Error on falsy values instead of stores passed to derived (#7947) breaking: Custom store implementers now need to pass an update function additionally to the set function ([#6750](https://github.com/sveltejs/svelte/pull/ 6750)) breaking: Do not expose default slot bindings to named slots and vice versa (#6049) breaking: Change order in which preprocessors are applied (#8618) breaking: The runtime now makes use of classList.toggle(name, boolean) which does not work in very old browsers ([#8629](https://github.com/sveltejs/svelte/ pull/8629)) breaking: apply inert to outroing elements (#8627) breaking: use CustomEvent constructor instead of deprecated createEvent method (#8775) These are just catch up releases, nothing seriously breaking. to give you perspective, Nodejs went from v10 to v20 in the same time frame.

In Svelte 4

its-summertime·Jun 14, 2023

> But not really - for any project of a significant size, sooner or later a build step will be needed for this or something else. Not to mention that many projects are now done in TypeScript, which means there's a build step anyway. https://github.com/sveltejs/svelte/pull/8569 > As a Svelte compiler developer, debugging without a build step greatly simplifies compiler development. Previously, debugging was complicated by the fact that we had to debug using the build step. In addition, using JSDoc does not affect compiler’s development safety because the type is almost equivalent to TS. Deno also switched away from using build-requiring TS

In ES Modules Are Terrible

popcalc·Jun 1, 2023Submission

Svelte 4 Breaking Changes

2 points · Open discussion

0xedb·May 31, 2023Submission

Svelte 4 is just around the corner

5 points · Open discussion

benmccann·May 10, 2023

Svelte will still provide type definitions. We're working on Svelte 4 currently and are taking the opportunity to make a few small breaking changes to the type definitions for improved TypeScript support: https://github.com/sveltejs/svelte/blob/version-4/CHANGELOG.... We'll cut a preview release soon and would love help testing and feedback from folks that have given it a try.

In TS to JSDoc Conversion

ajhenrydev·May 10, 2023Submission

TS to JSDoc Conversion

222 points · Open discussion

kodisha·May 9, 2023Submission

Svelte Moving from TS to JSDoc

7 points · Open discussion

pier25·Mar 27, 2023

> One example is being able to pass templates around. Yeah I agree. It's not a big deal but I kinda miss this from JSX. There was some discussion about adding templates or even components inside other components but it all feels very inelegant and not very Svelty. https://github.com/sveltejs/svelte/issues/2940

In Thoughts on Svelte

opensas·Mar 27, 2023Recommendation phrase

> The $ label is one technical reason why I would be hesitant to adopt Svelte for larger projects. It's a core part of Svelte that you can't always avoid, and I think the potential for introducing bugs through it is high to start and very high at scale. The reactivity system in Svelte is really a joy to use, once you get used to it there's no turning back. But the author did hit one of the ugliest pain points about it. Svelte can NOT correctly infer transitive dependencies when the variable being updated is inside a function. Meaning that the variable itself will be reactive (it will be invalidated every time it's assigned, even inside a function) but Svelte is not using that information to build the dependency graph, and falls back to the order in which the reactive blocks were defined, which may or may not be right. I created this issue

Read the rest

https://github.com/sveltejs/svelte/issues/5190 a couple years ago documenting it. It's not so common, but when it bytes you it's pretty nasty. The workarounds I found are the following These are the workarounds I found: - a repl with the issue: https://svelte.dev/repl/640736d3c91d40d3971afcc3eef8b25e?ver... - workaround 1: manually reorder statements, need to figure out by yourself (and maintain!) the dependency graph: https://svelte.dev/repl/3ecd6aa918e045999db32d379270fc1c?ver... - workaround 2 (my favorite): provide a redundant update as "hint" to tell the compiler that setY updates y: https://svelte.dev/repl/cbf98bb35f5e4dd4b037d13254853c90?ver... (thanks to TylerRick for this: https://github.com/sveltejs/svelte/issues/5190#issuecomment-...) in practice it means to do something like: `$: { setY(x); y = y };` - workaround 3: put the update operations in order in a single block (it's just the workaround 1 with improved legibility, IMHO): https://svelte.dev/repl/074df362bb934312bbe6fd3aeccab771?ver... I still think we could do better, at least explaining the issue and how avoid to fall into it (perhaps some linting warning?) But I really hope svelte developers start considering this an issue to solve, it's inconsistent (meaning the variable is reactive but that reactivity is not taken into account to order the operation in "topological order" (Hey, I learnt about that from one of Rich's presentations, see https://rethinking-reactivity.surge.sh/#slide=19) and as I said before, in the rare occasions you stumble upon it is not so easy to understand what's going on.

In Thoughts on Svelte

SebastianKra·Feb 3, 2023

Once a data is transformed into a view in Svelte, you can't do anything with it in JS. For example, a component can't iterate over the children in a slot [1]. This is limiting when designing generic Component-APIs. As an extreme example: In React, I could trivially define a tabbed interface by mixing strings, JSX, and components, without imposing any DOM-structure. The component that reads this definition could use it to build a tabbed-view on mobile, and a master-detail-view on desktop. ...or it could build a table of contents. When defining the tab names, I can mostly use strings, but fall back to JSX if necessary. Importantly, the API is completely independent from the implementation. const tabs = [ { name: "Tab 1", icon: <img ... />, content: MainTab }, { name: <>Tab with <b>bold<b/> text</>, icon: <MyIcon ... />, co

Read the rest

ntent: SecondTab }, ] return <MyLayout tabs={tabs} /> [1]: https://github.com/sveltejs/svelte/issues/5381

In Virtual DOM is pure overhead (2018)