CHALLENGE async function* gen() { const x = yield 1; const y = yield x + 1; return x + y; } async function main() { const it = gen(); const a = await it.next(); const b = await it.next(10); const c = await it.next(20); console.log(`${a.value} ${b.value} ${c.value} ${c.done}`); } main();

Channel
JavaScript
@javascript
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Telegram's recommendations · Cite this entry
31,076subscribers
-231 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 | -1001924414526 |
|---|---|
| Type | Channel |
| Usernames | @javascript @js_universe |
| Description | A resourceful newsletter featuring the latest and most important news, articles, books and updates in the world of #javascript 🚀 Don't miss our Quizzes! Let's chat: @nairihar |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 4 October 2026 |
| Measurements held | 67 |
| Confirmed unchanged | 1 time, most recently 4 October 2026 |
| On Telegram | t.me/javascript |
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 9 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Oct 2026, 19:58 | 31,076 | no change |
| 4 Oct 2026, 19:39 | 31,076 | -47 |
| 27 Sept 2026, 08:56 | 31,123 | -5 |
| 27 Sept 2026, 05:36 | 31,128 | -40 |
| 17 Sept 2026, 14:17 | 31,168 | no change |
| 17 Sept 2026, 12:36 | 31,168 | -3 |
| 15 Sept 2026, 11:17 | 31,171 | -1 |
| 15 Sept 2026, 08:20 | 31,172 | -4 |
| 13 Sept 2026, 22:18 | 31,176 | no change |
| 13 Sept 2026, 14:02 | 31,176 | -7 |
| 12 Sept 2026, 07:19 | 31,183 | -9 |
| 11 Sept 2026, 18:39 | 31,192 | -18 |
| 10 Sept 2026, 01:38 | 31,210 | -14 |
| 9 Sept 2026, 03:19 | 31,224 | -24 |
| 6 Sept 2026, 19:21 | 31,248 | -6 |
| 5 Sept 2026, 18:20 | 31,254 | +7 |
| 4 Sept 2026, 09:37 | 31,247 | -2 |
| 3 Sept 2026, 21:00 | 31,249 | +1 |
| 3 Sept 2026, 00:47 | 31,248 | -3 |
| 2 Sept 2026, 11:44 | 31,251 | first reading |
Engagement
157 posts held, back to 28 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 99 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.07%
- avg views ÷ 31,076 subscribers
- Avg views / post
- 1,570
- 59 posts measured
- Reaction rate
- 0.257%
- reactions ÷ views · ER floor
- Posts in window
- 59
- of 157 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. It is computed over the 50 of 59 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 October 2026 |
|---|---|
| Posts held | 157 (28 July 2026 – 6 October 2026) |
| Views total | 92,888 |
| Reactions total | 206 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Oct 2026, 00:12 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
- Photos
- ≈1,230
- Videos
- ≈10
- Links
- ≈899
Lifetime counters from Telegram’s own channel header, read 7 October 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
668 reactions across 137 posts, in 6 distinct kinds. The most used accounts for 46.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 311 | 46.6% | |
| 🔥 | 155 | 23.2% | |
| 👍 | 135 | 20.2% | |
| 🤣 | 31 | 4.64% | |
| 🤔 | 29 | 4.34% | |
| 🤩 | 7 | 1.05% |
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 143 of the 157 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 675 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 157 most recent posts we hold, published 28 July 2026 to 6 October 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
What is the output?
- 1 11 30 true32%
- 1 11 31 true32%
- undefined 11 30 true26%
- 1 10 30 true11%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
🎵 Tonny Espeset has recreated the '80s hit Take on Me by A-ha in pure JavaScript (along with synthesized vocals!), running through the always-entertaining Dittytoy online JavaScript music playground.
❤7
CHALLENGE class Base { static log = []; static { Base.log.push('base-block'); } static value = (() => { Base.log.push('base-field'); return 1; })(); } class Derived extends Base { static { Derived.log.push('derived-block'); } static value2 = (() => { Derived.log.push('derived-field'); return 2; })(); } console.log(Derived.log.join(','));
❤1
What is the output?
- base-block,base-field,derived-block,derived-field33%
- base-field,base-block,derived-field,derived-block38%
- base-block,derived-block,base-field,derived-field24%
- derived-block,derived-field,base-block,base-field6%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
👀 Size Limit: A JavaScript Performance Budgeting Tool Set a size or load-time budget for your code and this tool can fail CI (or flag a PR) if a change goes over it. You can also do one-off checks and see visualizations of where the bytes are. Framework-agnostic and doesn’t care which bundler or CI you use. Andrey Sitnik
❤1
What is the output?
- 49 2524%
- 19 6436%
- 64 1935%
- 81 95%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
CHALLENGE const compose = (...fns) => fns.reduce((f, g) => (...args) => f(g(...args))); const pipe = (...fns) => fns.reduce((f, g) => (...args) => g(f(...args))); const add1 = x => x + 1; const double = x => x * 2; const square = x => x * x; const composed = compose(square, double, add1); const piped = pipe(square, double, add1); console.log(composed(3), piped(3));
❤2👍1
🤩 The Grand Unifying Architecture of Frontend SolidJS's creator argues that HTMX, React, LiveView, and friends differ mostly in how they split the same three jobs (navigation, content, and instant UI feedback) between client and server. He then shows how Solid 2.0 aims to cover the whole spectrum. Ryan Carniato
❤3👍3
😮 How Anthropic Made Claude's Apps 3x Faster in Two Weeks A grab bag of performance lessons from a sprint that cut p75 'time-to-typeable' from 3.1s to 0.55s. Em dashes (the irony!) pushed V8 onto a slower regex path, a stray location.reload() caused half a million hidden reloads a day, and more. Wang, Attard, and G (Anthropic)
❤3👍3
What is the output?
- 2,4,6,8 1,2,3,4 1,2,3,437%
- 2,4,6 1,2,3 1,2,3,434%
- 2,4,6,8 1,2,3 1,2,3,416%
- 2,4,6 1,2,3 1,2,312%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
❤1
CHALLENGE const arr = [1, 2, 3]; const log = []; const result = arr.map((x, i) => { if (i === 0) arr.push(4); log.push(x); return x * 2; }); console.log(result.join(','), log.join(','), arr.join(','));
❤4🔥2👍1
Showing the 12 most recent of 157 posts we hold for @javascript. 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.
Polls
The 6 most recent of 65 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
What is the output?
- 1 11 30 true32%
- 1 11 31 true32%
- undefined 11 30 true26%
- 1 10 30 true11%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
What is the output?
- base-block,base-field,derived-block,derived-field33%
- base-field,base-block,derived-field,derived-block38%
- base-block,derived-block,base-field,derived-field24%
- derived-block,derived-field,base-block,base-field6%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
What is the output?
- 49 2524%
- 19 6436%
- 64 1935%
- 81 95%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
What is the output?
- 2,4,6,8 1,2,3,4 1,2,3,437%
- 2,4,6 1,2,3 1,2,3,434%
- 2,4,6,8 1,2,3 1,2,3,416%
- 2,4,6 1,2,3 1,2,312%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
What is the output?
- 1 2 121%
- 1 4 238%
- 2 2 226%
- 1 2 215%
Shares as published. No per-option vote count is published by Telegram, so none is shown.
What is the output?
- 6 4 😀20%
- 5 4 😀38%
- 6 5 😀22%
- 5 5 😀19%
Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 157 most recent posts we hold, published 28 July 2026 to 6 October 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@JavaScript_Trainings · 96,616#1
@webdevcoursefree · 79,588#2
@ready_dot_code · 8,469#3
@webdev_trainings · 133,869#4
@fedevelopment · 28,661#5
@front_end_first · 25,888#6
@javascript_courses · 55,709#7
@React_Training · 62,911#8
@C0DE_NET · 5,013#9
@everythingaboutcode · 9,548#10
@fulljavascript2023 · 11,440#11
@linkedin_learning · 217,941#12
@happywebdev · 15,070#13
@indianhtmlweb · 11,561#14
@oyaya17 · 2,447#15
@mern_mean · 5,935#16
@webde · 31,738#17
@web_dev_bds · 4,429#18
@frontend_info · 5,286#19
@Programming_experts · 67,911#20
@Codewithrandom · 229,782#21
@CodeDiksha · 3,099#22
@webdev_books · 9,034#23
@angular2 · 4,854#24
@synkrone · 1,025#25
@codescientist · 8,970#26
@explore_react · 4,468#27
@SoftSkills101 · 35,579#28
@computer_science_and_programming · 139,769#29
@OfficialCodingExpert · 3,240#30
@github_repos · 27,527#31
@cpp_programming_books · 5,396#32
@nextjss · 1,594#33
@reactnativeground · 2,156#34
@programming_guide · 56,004#35
@FrontWars · 4,378#36
@angular_practical_notes · 1,479#37
@frontend_trend · 19,053#38
@udemyrip · 68,318#39
@codingLikeGod · 2,741#40
@LearnPython3 · 125,109#41
@frontend · 3,355#42
@DeepDevs · 9,257#43
@sql_databases · 70,807#44
@CodeWithRadha · 1,107#45
@webdeveloperjob · 6,849#46
@mayoquz · 4,546#47
@unilance · 14,802#48
@sqlanalyst · 76,726#49
@ProjectsWithSourceCode · 2,565#50
@Javascriptproo · 4,094#51
@frontendchannels · 8,663#52
@CleverDevs · 10,928#53
@reactjs_support · 2,751#54
@javascriptv · 16,939#55
@cssWeb_Dev · 3,224#56
@jscriptandalgorithm · 5,529#57
@datasciencefree · 68,525#58
@aineeringdotcom · 16,044#59
@crackingthecodinginterview · 52,215#60
@ZTM_ACADEMY · 41,486#61
@Python53 · 51,064#62
@InterviewBooks · 40,500#63
@udemy_free_courses_with_certi · 70,672#64
@notificaJobs_react · 4,003#65
@devtwitter · 32,384#66
@seniorFront · 23,852#67
@CodingQuizZone · 1,551#68
@UmarSadullayev · 5,209#69
@frontEndJobo · 10,586#70
@frontendVacancy · 2,404#71
@UstozShogird · 22,971#72
@DevopsDoc · 9,850#73
@ddevjobs · 6,891#74
@AI_Agentic_Coding · 25,044#75
@dot_net_mvc · 8,394#76
Read from Telegram’s recommendation API, most recently 6 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@codehype · 23,427
Telegram ranks this channel #1 of 74 here — alongside 73 others — read 17 September 2026
@front_end_first · 25,888
Telegram ranks this channel #4 of 90 here — alongside 89 others — read 13 September 2026
@fedevelopment · 28,661
Telegram ranks this channel #5 of 88 here — alongside 87 others — read 9 September 2026
@JavaScript_Trainings · 96,616
Telegram ranks this channel #5 of 68 here — alongside 67 others — read 16 August 2026
@APP_Mastery · 39,690
Telegram ranks this channel #7 of 54 here — alongside 53 others — read 30 August 2026
@React_Training · 62,911
Telegram ranks this channel #7 of 64 here — alongside 63 others — read 21 August 2026
@SoftSkills101 · 35,579
Telegram ranks this channel #8 of 59 here — alongside 58 others — read 2 September 2026
@webde · 31,738
Telegram ranks this channel #9 of 84 here — alongside 83 others — read 5 September 2026
@CodingNews · 22,996
Telegram ranks this channel #11 of 68 here — alongside 67 others — read 19 September 2026
@Codewithrandom · 229,782
Telegram ranks this channel #11 of 83 here — alongside 82 others — read 11 August 2026
@webdevcoursefree · 79,588
Telegram ranks this channel #14 of 79 here — alongside 78 others — read 19 August 2026
@coding_knwledge01 · 78,396
Telegram ranks this channel #14 of 82 here — alongside 81 others — read 18 August 2026
@webdev_trainings · 133,869
Telegram ranks this channel #14 of 65 here — alongside 64 others — read 13 August 2026
@WebsiteDesignLearningGroup · 27,789
Telegram ranks this channel #16 of 63 here — alongside 62 others — read 10 September 2026
@javascript_courses · 55,709
Telegram ranks this channel #16 of 77 here — alongside 76 others — read 23 August 2026
@designwithrehana · 22,682
Telegram ranks this channel #18 of 77 here — alongside 76 others — read 19 September 2026
@aman_dhattarwal · 34,239
Telegram ranks this channel #24 of 51 here — alongside 50 others — read 3 September 2026
@placementducatindia · 36,207
Telegram ranks this channel #24 of 73 here — alongside 72 others — read 2 September 2026
@developperHome · 68,070
Telegram ranks this channel #30 of 83 here — alongside 82 others — read 20 August 2026
@the_coding_wizard · 177,960
Telegram ranks this channel #31 of 89 here — alongside 88 others — read 12 August 2026
@thedevs · 32,076
Telegram ranks this channel #33 of 82 here — alongside 81 others — read 5 September 2026
@webguild · 51,126
Telegram ranks this channel #39 of 86 here — alongside 85 others — read 24 August 2026
@ZTM_ACADEMY · 41,486
Telegram ranks this channel #42 of 54 here — alongside 53 others — read 29 August 2026
@webdevelopment657 · 22,266
Telegram ranks this channel #43 of 83 here — alongside 82 others — read 20 September 2026
This channel appears in 38 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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 4 October 2026 — this entry's latest reading, not the date you are reading this.
“JavaScript” (@javascript), 31,076 subscribers as measured 4 October 2026. Telegram Register, tgregister.com/channel/javascript.
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.