Telegram RegisterThe public register of Telegram

Channel

FrontEnd Development

@fedevelopment

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

28,851subscribers

-39 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001057630344
TypeChannel
Username@fedevelopment
CreatedBetween 1 May 2016 and 31 January 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held9
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/fedevelopment

Growth

28,85128,89528,8735 August 2026 — 28,890 subscribers6 August 2026 — 28,890 subscribers6 August 2026 — 28,895 subscribers7 August 2026 — 28,885 subscribers8 August 2026 — 28,880 subscribers9 August 2026 — 28,875 subscribers10 August 2026 — 28,868 subscribers11 August 2026 — 28,863 subscribers12 August 2026 — 28,851 subscribers5 August 202612 August 2026
9 measurements spanning 7 days, net -39. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 28,844–28,902 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 21:5828,851-12
11 Aug 2026, 21:4628,863-5
10 Aug 2026, 20:0828,868-7
9 Aug 2026, 23:3428,875-5
8 Aug 2026, 23:1428,880-5
7 Aug 2026, 21:0828,885-10
6 Aug 2026, 18:2628,895+5
6 Aug 2026, 02:0028,890no change
5 Aug 2026, 23:5228,890first reading

Engagement

20 posts held, back to 13 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 17 pagesof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 23 October 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

76 reactions across 20 posts, in 8 distinct kinds. The most used accounts for 39.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3039.5%
2634.2%
🔥810.5%
👏67.89%
😁33.95%
💯11.32%
🙏11.32%
🤔11.32%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 76reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 October 2025 to 23 October 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

23 Oct 2025, 05:00 UTC≈16,200 views12 reactionsread 12 August 2026

Nuxt Performance Performance best practices are now available in the Nuxt documentation. - https://nuxt.com/docs/4.x/guide/best-practices/performance #vue

11🔥1

21 Oct 2025, 10:00 UTC≈15,000 views7 reactionsread 12 August 2026

Performant Vue applications with Vapor In this article, you’ll explore why it is the future of both Vue and web development and will understand better if it will work for us. - https://dev.to/jacobandrewsky/performant-vue-applications-with-vapor-56f0 #vue

3👍3💯1

20 Oct 2025, 05:00 UTC≈12,400 views3 reactionsread 12 August 2026

Creating an Immersive 3D Weather Visualization with React Three Fiber - https://tympanus.net/codrops/2025/09/18/creating-an-immersive-3d-weather-visualization-with-react-three-fiber/ #react

👍3

19 Oct 2025, 10:00 UTC≈11,800 views4 reactionsread 12 August 2026

Optimizing Nuxt Server Side Rendering (SSR) Performance In this article, you'll explore techniques to optimize server-side rendering performance in the Nuxt framework. From efficient data fetching, caching, to smart deployments and edge rendering - https://www.debugbear.com/blog/nuxt-ssr-performance #vue

🔥21👍1

19 Oct 2025, 05:00 UTC≈7,840 views3 reactionsread 12 August 2026

Migrating a Project from Prettier and ESLint to Biome Prettier and ESLint are staples in many JavaScript build processes, but Biome offers an interesting ‘one stop shop’ alternative. - https://blog.appsignal.com/2025/05/07/migrating-a-javascript-project-from-prettier-and-eslint-to-biomejs.html #biomejs

👍21

18 Oct 2025, 10:00 UTC≈6,190 views3 reactionsread 12 August 2026

You May Be Looking for a useSyncExternalStore “when you see a useEffect that updates a useState and returns a value, you might be looking for a useSyncExternalStore.” - https://swizec.com/blog/you-may-be-looking-for-a-useSyncExternalStore/ #react

👍21

18 Oct 2025, 05:00 UTC≈5,330 views5 reactionsread 12 August 2026

Pompelmi: Scan File Uploads for Malware Provides adapters for Express, Koa, and Next.js to perform fast file-upload malware scanning in Node, including digging into ZIP files and with optional integration with the YARA malware detection tool. - https://pompelmi.github.io/pompelmi/ #nodejs

👍21👏1😁1

17 Oct 2025, 15:00 UTC≈4,930 views4 reactionsread 12 August 2026

I Think the Ergonomics of Generators is Growing on Me The author notes generator functions have been widely available in JavaScript for a long time, yet “their practicality hasn’t exactly caught on.” This is a great look at what they are and where they can be useful. - https://macarthur.me/posts/generators/ #javascript

👍3🔥1

17 Oct 2025, 10:00 UTC≈4,350 views2 reactionsread 12 August 2026

3D Layered Text: The Basics Amit Sheen explains how to build the layered 3D text effect from scratch using HTML and CSS, covering structure, stacking, indexing, perspective, and how to make it all come together visually. - https://css-tricks.com/3d-layered-text-the-basics #css

👍1🔥1

17 Oct 2025, 05:00 UTC≈3,850 views2 reactionsread 12 August 2026

What is useSlots in Vue? In this article, you’ll explore what useSlots is, when and how to use it, and provide practical examples to clarify its purpose. - https://dev.to/jacobandrewsky/what-is-useslots-in-vue-2hd #vue

1👍1

16 Oct 2025, 10:00 UTC≈3,730 views3 reactionsread 12 August 2026

Mastering npx: A Cheatsheet for npm and Node Power Users You’ve almost certainly used the npx command to easily run a command from an npm package (either local or remote) – it’s easy to use, but npx has a couple of other features and options to keep in mind. https://www.nodejs-security.com/blog/mastering-npx-cheatsheet-npm-nodejs-power-users #nodejs

👏2👍1

16 Oct 2025, 05:00 UTC≈3,390 views3 reactionsread 12 August 2026

Middleware Now Stable in React Router The middleware feature is now stable in React Router 7.9.0 via the future.v8_middleware flag. Here’s a look at the problems it can solve, and the patterns it unlocks. - https://remix.run/blog/middleware #react

👍3

Showing the 12 most recent of 20 posts we hold for @fedevelopment. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

TheSanskaarSingh
@codeslearningTG · 269,931
Telegram ranks this channel #19 of 84 here — alongside 83 others — read 11 August 2026
TCW - AI & Coding Resources 🚀👨‍💻
@the_coding_wizard · 182,622
Telegram ranks this channel #36 of 89 here — alongside 88 others — read 12 August 2026
Codewithrandom
@Codewithrandom · 235,492
Telegram ranks this channel #41 of 83 here — alongside 82 others — read 11 August 2026
Remote Jobs
@remotejobss · 157,302
Telegram ranks this channel #67 of 98 here — alongside 97 others — read 12 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.

“FrontEnd Development” (@fedevelopment), 28,851 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/fedevelopment.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.