en
Feedback
JavaScript

JavaScript

Open in Telegram

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

Show more

๐Ÿ“ˆ Analytical overview of Telegram channel JavaScript

Channel JavaScript (@javascript) in the English language segment is an active participant. Currently, the community unites 31 441 subscribers, ranking 4 377 in the Technologies & Applications category and 13 573 in the India region.

๐Ÿ“Š Audience metrics and dynamics

Since its creation on ะฝะตะฒั–ะดะพะผะพ, the project has demonstrated rapid growth, gathering an audience of 31 441 subscribers.

According to the latest data from 11 June, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -198 over the last 30 days and by 17 over the last 24 hours, overall reach remains high.

  • Verification status: Not verified
  • Engagement rate (ER): The average audience engagement rate is 6.20%. Within the first 24 hours after publication, content typically collects 2.53% reactions from the total number of subscribers.
  • Post reach: On average, each post receives 1 949 views. Within the first day, a publication typically gains 797 views.
  • Reactions and interaction: The audience actively supports content: the average number of reactions per post is 7.
  • Thematic interests: Content is focused on key topics such as javascript, console.log(gen.next().value, processdata, remix, acc.

๐Ÿ“ Description and content policy

The author describes the resource as a platform for expressing subjective opinions:
โ€œ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โ€

Thanks to the high frequency of updates (latest data received on 12 June, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.

31 441
Subscribers
+1724 hours
-587 days
-19830 days
Posts Archive
What is the output?
Anonymous voting

CHALLENGE

const temperature = {
  celsius: 22,
  [Symbol.toPrimitive](hint) {
    if (hint === 'number') {
      return this.celsius;
    }
    if (hint === 'string') {
      return `${this.celsius}ยฐC`;
    }
    return this.celsius + 273.15;
  }
};

console.log(`Temp: ${temperature}`);
console.log(temperature + 0);
console.log(temperature * 2);
console.log(+temperature);

๐ŸคŸ Evolving the Node.js Release Schedule: A Work in Progress The Node.js team has long been discussing shifting Node to a new
๐ŸคŸ Evolving the Node.js Release Schedule: A Work in Progress The Node.js team has long been discussing shifting Node to a new schedule of one major release per year (instead of two), removing the odd/even distinction, and making every release LTS (with a prior 11 months of alpha/current status). This is a preview post not intended for final publication till April, so things are subject to change (backup version). The Node.js Team

What is the output?
Anonymous voting

CHALLENGE
class EventEmitter {
  #listeners = new WeakMap();
  #registry = new FinalizationRegistry((label) => {
    console.log(`Cleaned up: ${label}`);
  });

  subscribe(target, callback) {
    if (!this.#listeners.has(target)) {
      this.#listeners.set(target, []);
    }
    this.#listeners.get(target).push(callback);
    this.#registry.register(target, target.name ?? "unknown");
  }

  emit(target) {
    const cbs = this.#listeners.get(target);
    if (cbs) cbs.forEach(cb => cb());
  }
}

const emitter = new EventEmitter();
let obj1 = { name: "sensor" };
let obj2 = { name: "timer" };

const ws = new WeakSet([obj1, obj2]);

emitter.subscribe(obj1, () => console.log("sensor fired"));
emitter.subscribe(obj2, () => console.log("timer fired"));
emitter.subscribe(obj1, () => console.log("sensor logged"));

emitter.emit(obj1);

console.log(ws.has(obj1));
obj1 = null;
console.log(ws.has({ name: "sensor" }));

๐Ÿฅถ Patreon has shared the tale of its seven year migration from JavaScript to TypeScript. There's a focus on tooling choices
๐Ÿฅถ Patreon has shared the tale of its seven year migration from JavaScript to TypeScript. There's a focus on tooling choices that might be useful if you're making a similar shift.

What is the output?
Anonymous voting

CHALLENGE

function Vehicle(make, model, year) {
  this.make = make;
  this.model = model;
  this.year = year;
  this.describe = function () {
    return `${this.year} ${this.make} ${this.model}`;
  };
}

Vehicle.prototype.age = function (currentYear) {
  return currentYear - this.year;
};

const car = new Vehicle("Toyota", "Supra", 1998);
const bike = new Vehicle("Harley", "Sportster", 2005);

console.log(car.describe());
console.log(bike.age(2025));
console.log(car.constructor === Vehicle);
console.log(Object.getPrototypeOf(car) === Vehicle.prototype);

๐Ÿ“ˆ In The 49MB Web Page, Shubham Bose expresses surprise at finding that loading a single NY Times page results in 422 networ
๐Ÿ“ˆ In The 49MB Web Page, Shubham Bose expresses surprise at finding that loading a single NY Times page results in 422 network requests and 49 megabytes of data transferred. He reflects on the problems that have led to this being a common experience on news sites.

What is the output?
Anonymous voting

CHALLENGE

const p1 = new Promise((resolve) => {
  console.log("A");
  resolve("B");
});

const p2 = p1.then((val) => {
  console.log(val);
  return "C";
});

p2.then((val) => {
  console.log(val);
});

console.log("D");

โœŒ๏ธ Temporal: The 9-Year Journey to Fix Time in JavaScript JavaScriptโ€™s date/time handling is notoriously messy and libraries
โœŒ๏ธ Temporal: The 9-Year Journey to Fix Time in JavaScript JavaScriptโ€™s date/time handling is notoriously messy and libraries like Moment.js became popular as a way to work around it. In 2017, Maggie Johnson-Pint, a maintainer of Moment.js, proposed the Temporal API to fix date/time handling for good, and weโ€™re mostly there (support is growing, with Safari and Node to catch up). Jason Williams (Bloomberg)

โœŒ๏ธ Temporal: The 9-Year Journey to Fix Time in JavaScript JavaScriptโ€™s date/time handling is notoriously messy and libraries
โœŒ๏ธ Temporal: The 9-Year Journey to Fix Time in JavaScript JavaScriptโ€™s date/time handling is notoriously messy and libraries like Moment.js became popular as a way to work around it. In 2017, Maggie Johnson-Pint, a maintainer of Moment.js, proposed the Temporal API to fix date/time handling for good, and weโ€™re mostly there (support is growing, with Safari and Node to catch up). Jason Williams (Bloomberg)

What is the output?
Anonymous voting

CHALLENGE


class AppError extends Error {
  constructor(message, statusCode) {
    super(message);
    this.name = this.constructor.name;
    this.statusCode = statusCode;
  }
}

class ValidationError extends AppError {
  constructor(message) {
    super(message, 400);
    this.fields = [];
  }
}

function riskyOperation(value) {
  if (value === null) throw new ValidationError("Null value");
  if (value < 0) throw new AppError("Negative value", 422);
  return value * 2;
}

const results = [];

for (const val of [10, null, -5, 3]) {
  try {
    results.push(riskyOperation(val));
  } catch (e) {
    if (e instanceof ValidationError) {
      results.push(`Validation:${e.statusCode}`);
    } else if (e instanceof AppError) {
      results.push(`App:${e.statusCode}`);
    } else {
      results.push("Unknown");
    }
  }
}

console.log(results.join(" | "));

What is the output?
Anonymous voting

CHALLENGE

const p1 = new Promise((resolve) => {
  console.log("A");
  resolve("X");
});

const p2 = p1.then((val) => {
  console.log("B");
  return val + "Y";
});

const p3 = p2.then((val) => {
  console.log("C:", val);
});

console.log("D");

What is the output?
Anonymous voting

CHALLENGE
"use strict";

function createCounter() {
  let count = 0;

  return {
    increment() { count++; },
    decrement() { count--; },
    getCount() { return count; },
    reset: () => { count = 0; }
  };
}

const counter = createCounter();
counter.increment();
counter.increment();
counter.increment();
counter.decrement();

const { getCount, reset } = counter;

console.log(getCount());
reset();
console.log(counter.getCount());