Telegram RegisterThe public register of Telegram
Telegram profile photo for Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js

Channel

Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js

@frontendproglib

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

20,975subscribers

-139 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001153356487
TypeChannel
Username@frontendproglib
Created23 July 2018measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live10 September 2026
Measurements held29
Confirmed unchanged2 times, most recently 10 September 2026
On Telegramt.me/frontendproglib

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

20,97521,11421,044.56 August 2026 — 21,114 subscribers6 August 2026 — 21,114 subscribers6 August 2026 — 21,112 subscribers7 August 2026 — 21,106 subscribers8 August 2026 — 21,107 subscribers9 August 2026 — 21,098 subscribers10 August 2026 — 21,097 subscribers11 August 2026 — 21,090 subscribers12 August 2026 — 21,088 subscribers14 August 2026 — 21,080 subscribers16 August 2026 — 21,074 subscribers17 August 2026 — 21,072 subscribers18 August 2026 — 21,078 subscribers19 August 2026 — 21,070 subscribers20 August 2026 — 21,068 subscribers22 August 2026 — 21,064 subscribers23 August 2026 — 21,053 subscribers25 August 2026 — 21,042 subscribers26 August 2026 — 21,039 subscribers27 August 2026 — 21,033 subscribers28 August 2026 — 21,030 subscribers29 August 2026 — 21,019 subscribers29 August 2026 — 21,015 subscribers31 August 2026 — 21,013 subscribers1 September 2026 — 21,006 subscribers1 September 2026 — 21,002 subscribers2 September 2026 — 20,989 subscribers4 September 2026 — 20,987 subscribers7 September 2026 — 20,975 subscribers6 August 20267 September 2026
29 measurements spanning 32 days, net -139. 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 20,954–21,135 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
7 Sept 2026, 01:3720,975-12
4 Sept 2026, 13:4220,987-2
2 Sept 2026, 23:2720,989-13
1 Sept 2026, 23:0621,002-4
1 Sept 2026, 02:0821,006-7
31 Aug 2026, 01:2521,013-2
29 Aug 2026, 23:2821,015-4
29 Aug 2026, 02:3521,019-11
28 Aug 2026, 02:5621,030-3
27 Aug 2026, 00:4721,033-6
26 Aug 2026, 01:4821,039-3
25 Aug 2026, 02:3621,042-11
23 Aug 2026, 14:3621,053-11
22 Aug 2026, 03:0621,064-4
20 Aug 2026, 17:1521,068-2
19 Aug 2026, 19:0421,070-8
18 Aug 2026, 15:3321,078+6
17 Aug 2026, 15:4621,072-2
16 Aug 2026, 07:2721,074-6
14 Aug 2026, 21:2721,080first reading

Engagement

40 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 59 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
7.81%
avg views ÷ 20,975 subscribers
Avg views / post
1,640
21 posts measured
Reaction rate
1.57%
reactions ÷ views · ER floor
Posts in window
21
of 40 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 3 September 2026
Posts held40 (27 July 20263 September 2026)
Views total34,402
Reactions total540
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 17:33 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
2m 28s
Average length
15s

Measured directly from 10 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

700 reactions across 40 posts, in 12 distinct kinds. The most used accounts for 28.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
20128.7%
🥰14120.1%
👍13819.7%
🔥13218.9%
😁385.43%
🤔243.43%
👾192.71%
🌚20.286%
👏20.286%
🎉10.143%
😍10.143%
🥱10.143%

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 40 of the 40 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 700 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 40 most recent posts we hold, published 27 July 2026 to 3 September 2026, 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

3 Sept 2026, 11:01 UTC732 views5 reactionsread 3 September 2026
Photo

✨ React Bits — 165+ готовых анимаций для React Библиотека с копипаст-готовыми компонентами для тех случаев, когда хочется добавить интерфейсу немного магии, но писать анимацию с нуля лень: → текстовые анимации и эффекты → интерактивные UI-компоненты → анимированные фоны → эффекты для изображений и видео → версии для JS/TS и CSS/Tailwind Компоненты можно устанавливать через CLI или просто забрать исходный код и ада

🥰3👍2

2 Sept 2026, 16:03 UTC≈1,080 views10 reactionsread 3 September 2026

✅ Правильный ответ: ❤️ 1 Почему: все три вызова используют значение count из текущего рендера. При count = 0 каждый вызов фактически планирует обновление до 1. Если заменить на: setCount(c => c + 1); setCount(c => c + 1); setCount(c => c + 1); тогда результатом будет 3. 📍 Навигация: [Вакансии] 🐸 Библиотека фронтендера #code_challenge

👍10

2 Sept 2026, 09:14 UTC≈1,210 views90 reactionsread 3 September 2026
Photo

Что выведет код? 🔥 — 3 ❤️ — 1 🥰 — 2 🤔 — ошибка 📍 Навигация: [Вакансии] 🐸 Библиотека фронтендера #code_challenge

74🔥12🤔4

31 Aug 2026, 11:11 UTC≈1,450 views7 reactionsread 3 September 2026
Video

😮 Visual Types: типизация через картинки Вместо чтения про "Union type позволяет переменной быть одним из нескольких типов" — видишь схему, и всё сразу понятно. Что покрывает: 🔤 Примитивы, объекты, массивы, Union/Intersection типы, дженерики — все базовые концепции. Полезно для начинающих в TypeScript или тех, кто запутался в терминологии. 🔗 Ссылка на гид 🐸 Библиотека фронтендера #readme #ts

👍4🥰3

30 Aug 2026, 12:01 UTC≈1,540 views17 reactionsread 3 September 2026
Photo

📍 Навигация: [Вакансии] 🐸 Библиотека фронтендера #pixel_pause

😁17

29 Aug 2026, 11:02 UTC≈1,590 views81 reactionsread 3 September 2026
Photo

🔥 — 1 2 5 3 4 ❤️ — 1 2 3 5 4 🥰 — 1 2 5 4 3 🤔 — 1 5 2 3 4 🐸 Библиотека фронтендера #code_challenge #js

🔥54🤔168👾2😍1

28 Aug 2026, 11:00 UTC≈1,610 views8 reactionsread 3 September 2026
Photo

🚀 В новой версии браузера сразу несколько полезных изменений для веб-интерфейсов: 🔵 autocorrect теперь можно контролировать прямо через HTML — для input, textarea и contenteditable. 🔵OpaqueRange позволяет работать с выделенными участками текста внутри input и textarea. Например, для подсветки текста, inline-подсказок и popover. 🔵Reference Target улучшает работу ARIA-ссылок с Shadow DOM — label, aria-labelledby и д

6🥰2

27 Aug 2026, 11:03 UTC≈1,520 views58 reactionsread 3 September 2026

📚 Читаете ли вы техническую литературу, чтобы прокачать свои навыки? ❤️ — да, постоянно читаю 👍 — иногда читаю 👾 — почти не обращаюсь к книгам, получаю знания из других источников Посоветуйте в комментариях книги, которые показались вам наиболее полезными. Больше полезных книг — у нас в канале @progbook 📍 📍 Навигация: [Вакансии] 🐸 Библиотека фронтендера #career_merge

👍31👾179🥰1

26 Aug 2026, 11:01 UTC≈1,660 views12 reactionsread 3 September 2026
Photo

⭐️ Как JavaScript исполняется под капотом V8 Вы пишите let x = 1 + 2, а под капотом V8 уже строит синтаксическое дерево, генерирует байт-код и думает, стоит ли компилировать это в машинный код. Что в карточках: — Как V8 парсит и интерпретирует код — Что делает TurboFan и зачем нужен байт-код — Как работает сборка мусора — И почему порядок добавления свойств в объект — это не мелочь Если хотите писать реально быстр

8👍2🥰2

25 Aug 2026, 08:31 UTC≈1,690 views14 reactionsread 3 September 2026
Video

🫧 Gooey-эффекты для React без мыла на тексте liquid-gooey превращает обычные React-компоненты в «жидкие» интерфейсы: элементы могут сливаться, тянуться друг за другом и плавно менять форму. 🤩 Morph — объединяет элементы в gooey-массу 🤩 Move — создаёт жидкий след за движущимся элементом 🤩 Dissolve — позволяет изображениям «растворяться» при контакте Эффект применяется к отдельному SVG-слою, а настоящий DOM остаётся

🔥74👏2🥰1

24 Aug 2026, 13:03 UTC≈1,630 views10 reactionsread 3 September 2026

⚡️ Контроль целевых браузеров сборки Если приложение «работает у вас», это не показатель. Важно понимать, под какие версии браузеров фактически собирается билд. npx browserslist Команда выводит реальный список целевых браузеров на основе .browserslistrc или package.json. ⏺ Это напрямую влияет на: — транспиляцию через @babel/preset-env — CSS-префиксы (Autoprefixer) — подключение polyfills — размер bundle Без пр

👍5🥰3😁2

24 Aug 2026, 07:04 UTC≈1,700 views9 reactionsread 3 September 2026
Photo

✏️ OTP-инпут, который вы усложняли зря Разделённые поля, кастомные маски, десятки строк JS и ещё одна зависимость в бандле — всё это часто делают ради обычного одноразового кода. ℹ️ Этот гайд показывает корректный, доступный и удобный OTP-инпут можно сделать на одном <input> — по стандартам, с автозаполнением и без фреймворков. 📍 Навигация: [Вакансии] 🐸 Библиотека фронтендера #read_watch

👍6🥰3

Showing the 12 most recent of 40 posts we hold for @frontendproglib. 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 7 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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.

Frontender's notes [ru]
@frontendnoteschannel_ru · 31,509
Telegram ranks this channel #6 of 95 here — alongside 94 others — read 6 September 2026
Библиотека программиста
@proglibrary · 78,398
Telegram ranks this channel #8 of 82 here — alongside 81 others — read 19 August 2026
NOP::Nuances of Programming
@nuancesprog · 56,655
Telegram ranks this channel #11 of 84 here — alongside 83 others — read 23 August 2026
Владилен: IT в эпоху AI
@vladm · 39,370
Telegram ranks this channel #15 of 96 here — alongside 95 others — read 30 August 2026
FrontEnd Development
@fedevelopment · 28,790
Telegram ranks this channel #16 of 88 here — alongside 87 others — read 9 September 2026
Библиотека питониста | Python, Django, Flask
@pyproglib · 37,446
Telegram ranks this channel #27 of 84 here — alongside 83 others — read 1 September 2026
Типичный программист
@tproger · 78,586
Telegram ranks this channel #29 of 95 here — alongside 94 others — read 19 August 2026
Frontend Portal
@FrontendPortal · 36,827
Telegram ranks this channel #33 of 90 here — alongside 89 others — read 1 September 2026
Вайб-кодинг
@vibecoding_tg · 62,342
Telegram ranks this channel #59 of 85 here — alongside 84 others — read 1 September 2026

This channel appears in 9 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 7 September 2026 — this entry's latest reading, not the date you are reading this.

“Библиотека фронтендера | Frontend, JS, JavaScript, React.js, Angular.js, Vue.js” (@frontendproglib), 20,975 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/frontendproglib.

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.