Node.js · Theory

Events

← All stacks

Theory

30/723

Events

Events is simple if you keep it on paper. Asha uses it for Asha walking through Events in a campus project.

For Events, npm is in play. Don’t blame it until you have traced Asha walking through Events.

Without Events, a campus project gets messy and Asha walking through Events is hard to trust.

Events shows up in a campus project. Name Asha walking through Events, not “a real-world scenario”.

Don’t do this with Events — only reciting the name of Events. Interviewers spot it in ten seconds.

After Events, Asha should still remember only reciting the name of Events.

Viva for Events: what it is → one Events step Asha can write from memory → the mistake (only reciting the name of Events).

Exam tip

Say Events in one breath, then one Events step Asha can write from memory, then only reciting the name of Events.

Example

// Events
const users = [
  { id: 1, name: "Asha" },
  { id: 2, name: "Ravi" },
];

function findUser(id) {
  return users.find((u) => u.id === id) ?? null;
}

console.log(findUser(2));
console.log(users.map((u) => u.name));

Events: find user 2, then list names. Say both prints.

Short notes

DefEvents — Asha uses it for Asha walking through Events in a campus project.
RuleEvents → one Events step Asha can write from memory.
RememberEvents + npm (a campus project).
UseEvents in a campus project (Asha walking through Events).
TrapEvents — only reciting the name of Events.
ExEvents → Asha walking through Events.

// Events const users = [ { id: 1, name: "Asha" }, { id: 2, name: "Ravi" }, ]; function findUser(id) { return users.find((u) => u.id === id) ?? null; } console.log(findUser(2)); console.log(users.map((u) => u.name));

Events

Example

Short notes

Questions

Events

Example

Short notes

Questions