
"Only one toast at a time": a newcomer's first open-source library got 560 stars in a week
What it is A zero-dependency web notification (toast) component library. Only one toast shows at a time, and new messages morph in place with a spring animation. It ships packages for React, Svelte, Vue, and vanilla DOM.
Why it took off "Toasts pile up and the one you need gets pushed off screen" is a problem every frontend developer has hit, and a 30-second demo with sound makes it click immediately. The author posted a long dev.to article and a Reddit thread on day one, got into the shadcn component directory and 21st.dev on day two, and was then reshared by Ali Bey, a shadcn curator, and Freek, a big name in the Laravel community.
BHow you could follow it Don't build another toast. Pick a frontend component whose default implementation is mediocre, make an opinionated argument, keep the core dependency-free with per-framework packages, and copy its first-week launch: a long-form post, subreddits, the shadcn directory, 21st.dev, and a 30-second demo with sound. Then wait for the curators to pick it up.
- Data (updated daily) · Repo created 2026-11-05 · 781 stars · 7 days +174
GitHub · stars Data 2026-11-06 → 2026-11-20 (15 days, 15 observations). Points before 10-28 come from deeply / archive backfill, not every day has one
Ding is a web notification (toast) component library that keeps only one message on screen and morphs new ones in place with a spring animation. The author is a Svelte freelance developer from Turkey with 40 GitHub followers, and this is the first library he has formally released. Toasts are one of the most crowded frontend categories, and Sonner alone gets 57.5M downloads a week. Ding's idea isn't new either; almost the same thing was built before, and those projects got 25 and 60 stars. It took off because of distribution: on day one he covered every channel, on day three a recommending account reshared it, and on day five a big account from another community did. Anyone can copy this approach, so here's a breakdown and whether you could do it yourself.
A dev.to post from Nov 5
On 2026 Nov 5 (UTC), Yusuf Cengiz created the repo and published the package to npm. npm rejected the original name, so he switched to a scoped one, @yusufceng1z/ding. Three hours later he posted a long piece on dev.to titled "Why I made my toast library show only one toast at a time". The opening two sentences were:
"Most toast libraries stack notifications. Three errors in a row and you get three toasts stacked on each other, and the one you actually needed has already been pushed off screen."
He then covered three things: the 30-line spring solver, how he "bakes" the spring curve into CSS with linear(), and how to keep an older async request from overwriting a newer message when two requests fight over the same toast. He also wrote a section on "the cost: you lose history," admitting that "if you need every message to stay on screen, a queue is the better design." The article ends with: "This is the first library I've published, and I'd love to hear where this design falls short."
The same day, he posted (with a screen recording) on Reddit's r/sveltejs and r/react, shared a "my first open-source library" post on LinkedIn, posted in the Turkish developer community Prototürk, and posted a video to the Web Design community from his own X account. His X account has only ever posted 28 times in total.
What it is
Works with a single <Toaster /> line and a toast.success('Saved') call, with no CSS to import and no other dependencies. The core is vanilla JS, with official packages for React, Svelte 5, Vue 3, and vanilla DOM.
- Only one, morphing in place: an "uploading" progress bar turns into "success" directly, an error morphs into an error message with a "retry" button, and a repeated message shows "×2" instead of popping up again.
- Makes sound: the website demo has audio. When a recommending account reshared it later, the original post read "morphs and sounds included."
- Ones that should stay don't disappear on their own: error, loading, and button toasts don't auto-dismiss; you close them yourself. Esc dismisses, Alt+T jumps focus into the toasts, and systems with reduced motion enabled automatically switch to a fade.
How the stars came in, day by day
| Date | Stars gained that day | What happened |
|---|---|---|
| 11-05 | Repo created | dev.to long-form post, two Reddit posts, LinkedIn, Prototürk, X |
| 11-06 | by day 46 | Listed in shadcn's component registry (one command installs it: npx shadcn@latest add @ding/ding), and on 21st.dev, with a "Copy prompt for Cursor / Claude Code" button on the page |
| 11-07 | +18 | Ali Bey (@alibey_10), who runs the daily shadcn UI picks account "shadcn 世界每日 UI 精选", posted a 30-second video: "new registry for toast notification with morphs and sounds included", 16k views, about 500 likes, 413 bookmarks |
| 11-08 | +39 | Afterglow; the author posted 0.0.3, then added accessibility |
| 11-09 | +48 | Freek Van der Herten (@freekmurze, of Spatie), a big Laravel-circle account, posted the link, 21k views, about 335 likes, 347 bookmarks, and also published a note on his blog freek.dev; Product Rally picked it up |
| 11-10 | +84 | Freek's post got auto-reposted by a pile of aggregator sites, and someone shared it on daily.dev; the author posted the Vue package |
| 11-11 | +191 | cssscript.com ran a long feature; a blog in Indonesia wrote a long post |
| Latest | +127 | By 11-11 the GitHub page showed 564 stars and 16 forks |
(GitHub star counts are recorded daily; the numbers on X posts are what 11-11 saw.)
The curve climbs in steps, and each step lines up with a repost: after Ali Bey, daily gains hit +39 and +48; after Freek, +84 and +191. It wasn't on Hacker News, got no press coverage, and ran no ads.
Two things are worth noting. First, Ali Bey's post used the word "registry", and the timing falls on the day after Ding entered shadcn's directory. These daily-pick accounts need new material every day, and shadcn's registry is one of their supply sources, so he probably found it there (inference). Second, Freek's blog has a "community submission link" entry; whether Freek found it himself or the author submitted it can't be determined.
Bookmarks on both big-account posts nearly match their likes, suggesting the reaction was "save it for later". Under Freek's post, someone also tagged Livewire's author Caleb Porzio, urging him to use it in his Flux Pro component library.
Same idea, and the others only got 25 stars
"Physical spring + toast that morphs" wasn't Ding's invention. Back in February, Sileo caught fire on a single X post from its author and now has 1,820 stars. The core claim "only one visible at a time, morphing in place" was done in October by a library called notch-toast, nearly the same approach, now at 60 stars. The closest is February's Physics-Toast: zero-dependency vanilla JS, real springs, Dynamic Island-style morphing, even the same "Sonner alternative" pitch, promoted only once on cssscript, 25 stars.
So what did Ding do that they didn't?
One: it turned a trade-off into a position. It doesn't say "a better toast"; it says "I'm tired of toasts piling up, so I built one that doesn't." The dev.to long-form post lays out the costs too, which makes people who know the field willing to believe it and repost it.
Two: it landed on the sites recommenders check the next day. shadcn's component registry and 21st.dev are where accounts like Ali Bey's hunt for material every day. goey-toast also got into shadcn's registry back in February, but that ecosystem wasn't as hot then.
Three: it caught people React ignored. Sileo, notch-toast, and goey-toast are all React-only and depend on the motion animation library. Ding has zero dependencies, and one core ships as packages for four frameworks. The author writes Svelte, and the first post went out on r/sveltejs; Freek's post carried the #Svelte tag. On day three a Vue user asked for a Vue version, and on day six the author shipped it.
Four: built for AI coding tools. The site has an llms.txt (a spec file written for AI to read), indexed by context7, and 21st.dev offers a one-click copy prompt. Many people now have Cursor or Claude Code install components for them, and these are the hooks that get the AI to pick it. How much this contributed to the star count can't be measured.
Five: a newcomer who acts like a seasoned maintainer. In its first week it shipped 4 versions, and outside PRs were merged the same day. From day three to day five, an outside contributor named tcisse opened 7 PRs in a row (CI, i18n, Next.js docs, CSP, and more).
Also, the sitemap lists 13 landing pages aimed at search traffic: sonner-alternative, react-hot-toast-alternative, nextjs-toast, toast-vs-snackbar… The library is only a week old, so how much traffic those pages bring isn't clear yet.
Lots of bookmarks, fewer users
Across four npm packages, daily downloads ran 11-06 to 11-10 to 169 to 1,679 (the 1,468 on release day were mostly mirror syncs). Sileo over the same period did 3,858 to 15,395 a day, and Sonner does 57.5M a week. Ding's star count is running far ahead of its real usage. A third-party project (Trenova) is already using it in its code.
For an open-source author who wants stars, that's not bad news, since stars mostly come from "looks good, bookmark it." But it also shows a small component like a toast is hard to defend: Sonner is shadcn/ui's default toast, and switching away from it takes a strong reason.
Who else is in the space
| Project | Scale | Versus Ding |
|---|---|---|
| Sonner | 13.2k stars, npm 57.5M a week | shadcn/ui's default toast, stacking; Ding built a sonner-alternative page to intercept its search traffic |
| react-hot-toast / react-toastify | 11k / 13.4k stars | Long-established stacking toast, no physics animation |
| Sileo(2026-02) | 1,820 stars, now gaining only 0–6 a day | Closest predecessor: spring + morphing, React-only; the community has ported it to Svelte, Angular, Solid, Flutter, and Vue |
| goey-toast(2026-02) | 1,343 stars, growth has stopped | Adds liquid morphing on top of Sonner; still stacking, React-only |
| notch-toast(2026-10) | 60 stars | Nearly the same core claim (one at a time, morphing in place), no distribution push |
| Physics-Toast(2026-02) | 25 stars | Nearly the same positioning (zero-dependency, springs, Sonner alternative), relying on a single channel |
(GitHub stars and npm downloads, as of October 11-11.)
Ding has the most stars of any toast library created since August, and nobody has ported or copied it yet. But this category has a strong porting habit: once Sileo caught fire, the community released five or six framework versions of it, so it's only a matter of time before Ding's ideas get borrowed.
If it were you
B: this playbook is cheap and copyable, but the toast niche is full, so you'd need a different component category, and whether it takes off depends on whether recommender accounts pick it up. Don't build another toast. What's worth copying is the whole launch sequence, applied to other frontend components.
Who it suits: developers who can build polished frontend components and want a project of a few hundred to a thousand-plus stars on their resume and a bit of a following; especially people who write Svelte, Vue, or Solid, where good-looking components are scarcer than in React and recommender accounts are short on material.
Who it doesn't suit: anyone who wants to build in the toast or spring-animation space (Sonner, Sileo, and Ding already hold those spots); anyone who can't make a 30-second demo that's clear and attractive at a glance; anyone unwilling to spend the first week posting, submitting to directories, and answering issues.
How to do it: three ways to follow, best to worst:
- Switch categories, copy the playbook: pick a component everyone uses but whose default implementation is mediocre, such as date pickers, command palettes, file uploads, form validation messages, copy buttons, or skeleton screens. Find a claim that takes a stance, like Ding's "only one visible," one you can state in a sentence and that people can argue about.
- Zero-dependency core + thin framework wrappers: write the core in plain TS, and ship thin packages for React, Svelte, Vue, and vanilla DOM. Look for popular components that are React-only and depend on motion; the people they leave out are your users.
- Fill in what Ding hasn't done: some people want Angular, Solid, or React Native versions, which Ding doesn't have yet. Porting it is the fastest way to collect stars, but it has the lowest ceiling (Sileo's community ports mostly got a few dozen to a few hundred stars).
How to get users: follow Ding's timeline. Day one: publish a long-form post on dev.to about the trade-offs, post in relevant subreddits with a video, and put single posts on LinkedIn, native-language developer communities, and X. Day two: get into shadcn's component registry (packaged as a registry, installable with one command) and list on 21st.dev. Record a 30-second demo with sound so daily-pick accounts like Ali Bey's can repost it straight away. Put an llms.txt on the site, submit it to context7, and build a few "<big brand>-alternative" and "<framework>-<component>" landing pages. Submit to blogs with contribution entries like freek.dev. When people ask for something, ship it within days.
Timing: shadcn's component registry and 21st.dev are hot right now, and the daily-pick accounts are short on new material. The bar for recommender accounts rises once the registry fills with similar components, so aim to launch before the first quarter of 2027.
Signs you've misread it: (1) a mid-sized daily-pick account reposts you and you still haven't reached 100 stars a week later, which means this kind of component is no longer novel; (2) you've been listed in the shadcn registry and 21st.dev for two weeks with no daily-pick account reposting, which means the supply side is saturated and listings alone aren't enough; (3) conversely, if Ding keeps gaining stars steadily a month or two out and its npm downloads catch up with Sileo's, it means the "one visible toast" stance has real users and the toast niche isn't full yet, and building for the frameworks it doesn't cover would be worth more than estimated here.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one emilkowalski/sonner Open source 2023-02 13.2K stars; npm 57.5M a week; shadcn/ui default toast Stacking; Ding built a sonner-alternative landing page to capture traffic timolins/react-hot-toast Open source 2020-12 11.0K stars; npm 4.92M a week Stacking, no physics animation fkhadra/react-toastify Open source 2016-11 13.4K stars; npm 5.05M a week Long-established stacking toast, many features, dated styling notistack Open source 2018-08 4.1K stars; npm 2.8M a week MUI-style snackbar, stacking vue-sonner / svelte-sonner Open source 2023 1.5K / 1.3K stars; npm 3.21M / 880k a week Framework ports of Sonner, stacking; Ding's single core covers four frameworks hiaaryan/sileo Open source 2026-02-08 1,820 stars (now gaining 0–6 a day); npm 4K–15K a day Closest predecessor: physical springs + SVG gooey morphing, but React-only, depends on motion, allows multiple toasts; Ding is zero-dependency, multi-framework, enforces one at a time anl331/goey-toast Open source 2026-02-14 1,343 stars (growth stopped); npm 20k a week Blob morphing built on sonner + framer-motion; still stacking, React-only Devsethi3/notch-toast Open source 2026-10-19 60 star Nearly identical core idea (one at a time, morphing in place, notch-style toast), React + motion, no distribution push, didn't take off vorojar/Physics-Toast Open source 2026-02-17 25 star Nearly identical positioning (zero-dependency vanilla JS, real springs, Dynamic Island morphing, Sonner alternative), only a cssscript listing as its channel, serves as a counterexample for Ding shadcn/ui's built-in Sonner, MUI Snackbar, Chrome's official toast guide Big-company features Long-term / 2026-11-09 Default components / system-level Gives the default component or pattern only, with no single-toast morphing and no spring animation - Where users come from
- Verified Author self-launched across multiple platforms: on launch day 11-05 published a long dev.to post (on the spring solver and trade-offs), a video post on Reddit r/sveltejs + r/react, a LinkedIn post "my first open-source library", a post on the Turkish community Prototürk, and a video post in the Web Design community from his own X account
- Verified shadcn registry directory + 21st.dev: 11-06 commit added the registry item/index, so `npx shadcn@latest add @ding/ding` works; 21st.dev 11/6 listed it, with "copy prompt for Claude Code/Cursor"; the author posted on X "featured on @21st_dev"
- Verified Retweeted by shadcn curator @alibey_10: 11-07 posted a 30-second video, "new registry for toast notification with morphs and sounds included", with 16.1K views, about 496 likes and 413 bookmarks, the day after it entered the registry directory
- Verified Laravel-circle account @freekmurze + freek.dev blog: 11-09 posted a link, with 20.9K views, about 335 likes and 347 bookmarks; freek.dev/3216 was auto-reposted by engineered.at, devfeed, worldprogramming and Threads; compared with the 11-10 and 11-11 snapshots, +84 / +191
- Verified Aggregators and directories: Product Rally (11-09), daily.dev (11-10 entries), cssscript.com (11-11), bestofjs, trendshift, githubsignals, context7; a long post on an Indonesian blog
- Inferred Programmatic SEO and entry points for AI agents: the sitemap has 13 landing pages (sonner-alternative, react-hot-toast-alternative, svelte-sonner-alternative, nextjs-toast, toast-vs-snackbar…), plus /llms.txt; it has only been up 7 days, and how much search traffic it brings cannot be verified
- Inferred HN / TikTok / paid promotion: Algolia finds no HN post; TikHub finds no TikTok video; no ads were seen
YusufCeng1z/ding: shows only one toast at a time, and new notifications morph in place with spring physics
Research date 2026-11-11. Repo github.com/YusufCeng1z/ding, site ding.yusufcengiz.dev, npm@yusufceng1z/ding(core) /-react/-svelte/-vue, MIT.
Bottom line
Ding is the first officially released library from Yusuf Cengiz, a Turkish front-end developer who spent five years doing Svelte contract work (X alt account @josephJK_, 40 GitHub followers). It reached 550+ stars in 7 days in the extremely crowded toast category. The reason isn't a new idea: "physics spring + morphing toast" was already made popular by Sileo (1.8K stars) back in 2026 February, and "one at a time, morphing in place" was done by notch-toast in October. The reason is that three things came together:
- A claim you can explain in one sentence: "I got tired of toasts piling up, so I built one that doesn't pile up," with a 30-second screen recording that has sound;
- Covered the developer discovery channels on day one: a dev.to long post, Reddit r/sveltejs + r/react, LinkedIn, the Turkish community Prototürk, and posts on the author's X account. On day two it was listed in the shadcn registry directory and 21st.dev (with "copy prompt for Cursor / Claude Code"), plus llms.txt, context7, and a dozen "sonner-alternative / react-hot-toast-alternative" SEO landing pages;
- Relayed by two mid-sized curation accounts: 11-07 Ali Bey, the daily curator of the shadcn community (16K views, about 500 likes, 413 bookmarks), and 11-09 Freek Van der Herten of the Laravel community (21K views, about 335 likes, 347 bookmarks) plus his freek.dev blog. daily.dev, cssscript and other aggregators then copied it automatically.
The star curve is a stepped acceleration, wave after wave (+18 → +39 → +48 → +84 → +191 → +127). Each step lines up with a relay source. It isn't organic spread, and it isn't a single spike.
1. Data
- GitHub stars (our github repo_day, snapshot days): 11-06 46 → 11-07 64 (+18) → 11-08 103 (+39) → 11-09 151 (+48) → 11-10 235 (+84) → 11-11 426 (+191) → 11-12 553 (+127). The GitHub API 11-11 live shows 564 stars, 16 forks, 3 watchers. The repo was created 11-05, under 60 days old, so it can't hit trending (trending only includes repos about 60 days old, per the repo notes).
- Comparables (same repos, starting 10-28): Sileo gains only 0–6 stars a day, goey-toast is essentially flat, Sonner gains 2~12 a day, and notch-toast (created 10-19) has gained 0 in the past two weeks. Ding has the most stars of any toast library created since 2026-08 (GitHub search created>2026-08-01; the runner-up has 137 stars and isn't a UI library).
- npm downloads (api.npmjs.org, four packages combined): 11-05 1,468 (launch day, mostly mirrors), 11-06 169, 11-07 369, 11-08 1,148, 11-09 652, 11-10 1,679 (the Vue package's first day was 206). Compare Sileo at 3,858–15,395 per day over the last 10 days, goey-toast at 20k per week, and Sonner at 57.5M per week. Ding's real usage is still small, and its stars are well ahead of actual use.
- Community participation: 9 of 24 issues/PRs came from outside. tcisse opened 7 PRs in a row on days 3–5 (CI, i18n, Next.js docs,
"use client", CSP nonce, render tests). reslear asked for Vue support (the author shipped ding-vue on day 6). MathiasWP reported a demo flicker bug, and AqueleHaru asked for a border-radius variable. A third-party project, emoss08/Trenova, already references it in its code (GitHub code search). - Author background: 33 public repos. The best previous one was svelte-bash with 104 stars (2025-12 did a Show HN, 2 points), and svelte-gsap-template with 44 stars. 642 LinkedIn followers, and the X account has only 28 posts. 42 School students. No big-account backing.
2. Competitors (doing the same thing)
| Name | Where | Launched | Scale | How Ding differs |
|---|---|---|---|---|
| emilkowalski/sonner | Open source / npm | 2023-02 | 13.2K stars; npm 57.5M a week; shadcn/ui default toast | Stacked; Ding openly positions itself as a sonner-alternative |
| timolins/react-hot-toast | Open source / npm | 2020-12 | 11.0K stars; 4.92M per week | Stacked, no physics animation |
| fkhadra/react-toastify | Open source / npm | 2016-11 | 13.4K stars; 5.05M per week | Long-established stacked toast |
| notistack (MUI ecosystem) | Open source / npm | 2018-08 | 4.1K stars; 2.8M per week | Material-style snackbar stacking |
| vue-sonner / svelte-sonner | Open source / npm | 2023 | 1.5K / 1.3K stars; 3.21M / 880k per week | A framework port of Sonner, stacked |
| hiaaryan/sileo | Open source / npm | 2026-02-08 | 1,820 stars; 4K–15K npm per day; currently gaining 0–6 stars a day | Closest predecessor: a physics-spring + SVG gooey morphing toast. The author's X post drove its initial traction. React only, depends on motion. Svelte/Angular/Solid/Flutter/Vue community ports already exist. |
| anl331/goey-toast | Open source / npm | 2026-02-14 | 1,343 stars; 20k per week | Blob morphing built on sonner + framer-motion. Still stacked. Listed in the shadcn registry. Reposted by IG/FB accounts. |
| Devsethi3/notch-toast | Open source / npm | 2026-10-19 | 60 star | Almost the same core idea: a notch-style toast that shows one at a time and morphs in place. React + motion, and a Vue port called notch-toast-vue exists. It didn't take off. |
| vorojar/Physics-Toast | Open source | 2026-02-17 | 25 star | Almost the same positioning: zero-dependency vanilla JS, real springs, a Dynamic Island morph, and a "Sonner alternative". Promoted by cssscript/jQueryScript. It didn't take off. |
| Meerzus/cloudlet toast, srdavo/super-beautiful-toast | Open source | 2026-10-29 / 2026-08-22 | 41 / 26 star | Dynamic Island-style / Vue physics spring where a button turns into a toast |
| Chrome's official toast guide, MUI Snackbar, shadcn/ui's built-in Sonner | Big-company features | 2026-11-09 and others | System level | Gives code or default components, with no "single toast morphing in place + spring" |
Takeaway: Ding's two selling points had already been built before it, and some were built almost identically (Physics-Toast, notch-toast). Those projects got 25 and 60 stars. So the differentiation isn't in the idea.
3. Growth tactics (by time)
| Time (UTC) | Action | Evidence |
|---|---|---|
| 11-05 07:04–11:26 | Created the repo, published to npm (the original name was rejected by npm, so it moved to a scoped package), rewrote the README, swapped in a real screen-recording GIF, added a social preview image | Commit history |
| 11-05 10:11 | A dev.to long post, "Why I made my toast library show only one toast at a time", covering 30-line spring solver, CSS linear() baking of springs, and caller-id race prevention, and openly discussing the trade-offs | dev.to |
| 11-05~06 | Posted in Reddit r/sveltejs and r/react (alt account u/soyluhaliyikama, with video); LinkedIn "my first open-source library"; posted to Prototürk (Turkish developer community); video post in the Web Design community from the author's X account | Brave/Jina search results, LinkedIn, prototurk, x.com/josephJK_; bluvy.app 11-06 has a video mirror. Reddit vote counts unavailable (blocked by Reddit) |
| 11-06 09:35–10:50 | Added the shadcn registry item + registry index and entered the shadcn registry directory (npx shadcn@latest add @ding/ding); listed on 21st.dev the same day ("copy prompt and paste into Claude Code / Cursor / Lovable"); added SEO meta and sitemap | commit, 21st.dev "Published 11/6/2026" |
| 11-07 09:53 | @alibey_10 ("shadcn World's Daily UI Picks", makes shoogle.dev) posted a 30-second video: "new registry for toast notification with morphs and sounds included", 16.1K views, about 496 likes, 35 reposts, 413 bookmarks | x.com/alibey_10/status/2119005289865486565. The original uses the word "registry", and the timing is the day after it entered the shadcn directory. It likely came from the registry directory (inferred) |
| 11-08 | 0.0.3: accessibility (Alt+T, 44px click area, Esc rules), translatable labels, What's new with a live demo | commit |
| 11-09 01:12 | Featured on Product Rally (hunter Denis) | productrally.com/p/ding |
| 11-09 02:47 | Reposted by @so_sthbryan (with a shoogle.dev directory link, possibly repeating Ali Bey's content) | x.com/so_sthbryan |
| 11-09 12:31 | @freekmurze (Spatie, a major Laravel-community account) shared the link: 20.9K views, about 335 likes, 26 reposts, 347 bookmarks; freek.dev blog also published a post; in the replies, @calebporzio suggested Flux Pro use it | x.com/freekmurze/status/2119769746409197857, freek.dev/3216. freek.dev has a "community submission" entry, so it's unclear whether the author submitted it themselves |
| 11-09~10 | Freek's post was auto-reposted by engineered.at, devfeed.tech, worldprogramming, bubbles.town, Threads, and others; two daily.dev users shared it 11-10 times | Exa search results |
| 11-10 | Published ding-vue (responding to reslear's request), 0.0.4, added CSS variables to the docs | commit / npm |
| 11-11 | A feature article on cssscript.com ("Recommended"); an Indonesian blog, abdasis.my.id, wrote a long post | Exa |
| Ongoing | 13 programmatic SEO pages: react-toast, svelte-toast, nextjs-toast, shadcn-toast, javascript-toast, sonner-alternative, react-hot-toast-alternative, svelte-sonner-alternative, toast-vs-snackbar, undo-toast, loading-toast, toast-accessibility, toast-notification-ux; llms.txt; indexed by context7; auto-listed on bestofjs, trendshift, githubsignals | sitemap.xml, /llms.txt, search results |
Not found: no Hacker News post (Algolia search returned nothing); TikTok search returned nothing; no paid promotion; our local x-radar corpus didn't pick up any related posts.
The star steps match the repost sources: 11-07 Ali Bey → 11-08, 11-09 snapshot +39 / +48; 11-09 Freek + blog + aggregators → 11-10, 11-11 snapshot +84 / +191; 11-10 daily.dev, Vue package → 11-12 snapshot +127. We can't get stargazer timestamps (this endpoint returns 404 for our token), so the matching is only by day.
4. Why it took off
- Simple claim, a demo you understand at a glance. "Toasts pile up and the one you need gets pushed away" is something every frontend dev has hit; "keep just one, morph it in place" says it in one line. In the 30-second screen recording, the progress bar turns into success, errors get a retry button, and it plays sounds. Ali Bey's post said "with morphs and sounds included", and the bookmark counts on the two big-account posts (413, 347) are close to the like counts, which means people were saving it "to use later".
- Fast, broad distribution that targets where curator accounts go looking. On day 2 it entered the shadcn registry directory and 21st.dev; on day 3 the shadcn curator account reposted it. These accounts need new things to post every day, and registry directories are their supply. goey-toast was also listed in the shadcn registry, but back in February that directory ecosystem wasn't as hot as it is now.
- Built for AI coding agents. llms.txt, context7, a "copy prompt" on 21st.dev, and a README that spells out how to use it with the Next.js App Router. By 2026 many people had Cursor / Claude Code install components for them, and these are entry points that get the agent to pick it (their contribution to stars can't be quantified).
- Multi-framework plus zero dependencies, serving the people Sonner/Sileo didn't. Sileo, notch-toast, and goey-toast are all React + motion. Ding's core has zero dependencies, with official packages for React, Svelte 5, Vue 3, and vanilla DOM. The author is a Svelte developer and posted first on r/sveltejs; Freek's post used the #Svelte tag; a Vue community member (reslear) asked for a Vue package on day 3, and the author shipped it on day 6.
- Trust built through craft and response speed. A long dev.to post explains race-condition handling and the tradeoffs; 4 releases in one week, external bugs fixed and merged the same day; external contributors showed up by day 3. It's a newcomer's first library, but it reads like a mature maintainer's.
5. What's the differentiation, and is it why it broke out?
- Not a new idea: a physics-spring morphing toast = Sileo (2026-02,1.8K stars), already a hit; "one toast at a time, morphing in place" = notch-toast (2026-10,60 stars); "zero-dependency vanilla JS + spring + morph + Sonner alternative" = Physics-Toast (2026-02,25 stars). The last two pitched nearly the same selling points and didn't take off.
- The real differences: (a) it treats "single toast" as a clear product stance and explains the tradeoffs in a long post; (b) a zero-dependency core plus official packages for four frameworks, while rivals are React-only and depend on motion; (c) polish in the details: sound, progress bar, undo, caller ownership to prevent races, accessibility, CSP nonce, styles injected by JS so no CSS import is needed; (d) distribution packaging: shadcn registry, 21st.dev, llms.txt, SEO landing pages.
- Bottom line: product polish is what makes curator accounts willing to repost, but the direct cause of the breakout was (d) plus the author's multi-channel launch, which put it in front of curator accounts like Ali Bey and Freek, who look for new finds every day. Physics-Toast is the best counterexample: nearly the same positioning, but only one channel (cssscript), and 25 stars.
6. How many people know about it
- Word of mouth in niche circles: two mid-sized X posts (16k and 21k views), freek.dev, daily.dev, cssscript, auto-listed on bestofjs/trendshift; not on HN, no press, not on trending (under 60 days old). Open source and free, with no revenue.
- Copycats: none yet (a GitHub search for Ding-related ports returns zero). But the category itself is prone to porting: Sileo already has five or six community ports (Svelte, Angular, Solid, Flutter, Vue), so there's a high chance Ding gets ported or has its ideas borrowed once it takes off. On the flip side, Ding is itself riding the "physics toast" wave that Sileo started.
7. What others can learn
- In a red-ocean category, take one clear stance: don't say "a better toast"; say "only show one", a debatable position with tradeoffs, and explain the tradeoffs thoroughly in a long post (the dev.to article is where the credibility comes from).
- Cover the curators' supply within 48 hours of launch: dev.to, relevant subreddits, LinkedIn, native-language communities, X communities; on day 2 get into the shadcn registry directory and 21st.dev; record a 30-second video with sound so others can repost it directly.
- Distribution built for agents: llms.txt, context7, one-command install from the registry, a "copy prompt", and framework-specific guide pages (e.g., Next.js App Router).
- Programmatic SEO to capture traffic: long-tail pages like "<big brand>-alternative", "<framework>-toast", and "toast-vs-snackbar", live the day after the repo was created.
- Fast response to community requests to earn outside contributions: when someone asked for Vue, it shipped 3 days later; external PRs merged the same day.
- Zero-dependency core + thin multi-framework wrappers: directly serves Svelte and Vue users, groups that React-first libraries overlook.
8. Still unclear
- The exact daily source of stars (stargazer timestamps unavailable); the vote counts on the two Reddit posts (Reddit blocks scraping); the view count on the author's X launch post.
- Whether Freek discovered it on his own or the author submitted it through the freek.dev community link; whether Ali Bey found it through the shadcn registry directory (the post used the word "registry" and the timing fits, but this is inference).
- How many npm downloads are real users (about 1,500 downloads on the release day look like mirrors), and how well it retains; 7 days of data is too short to know how long the buzz will last.
- Category ceiling: generic toast components are hard to build a moat around. Sonner is the shadcn default, and Sileo already has 1.8K stars and tens of thousands of daily downloads.