Why does a Promise callback run before setTimeout?

Promise callbacks are microtasks, and `setTimeout` callbacks are macrotasks. After each task finishes, the event loop drains the entire microtask queue before running the next macrotask or rendering. So a resolved promise's `.then` always executes before a `setTimeout(fn, 0)`, even when both are scheduled at the same moment.

Is JavaScript single-threaded or multi-threaded?

JavaScript executes your code on a single main thread using an event loop, so only one piece of code runs at a time. Concurrency comes from offloading work to the host environment, such as timers, network requests, and Web Workers. Workers run on separate threads but communicate through messages, not shared call stacks.

How do I find and fix memory leaks in JavaScript?

Take heap snapshots in the browser DevTools Memory panel and look for objects that grow over time or stay retained after they should be freed. Common causes are uncleared timers, dangling event listeners, detached DOM nodes, and unbounded caches. Clean up listeners and intervals, and use `WeakMap` or `WeakSet` for collectible references.

How do I run async operations in parallel?

Start the operations without awaiting each one immediately, then await them together with `Promise.all`. For example, `await Promise.all([fetchA(), fetchB()])` runs both concurrently. Awaiting inside a loop serializes calls and is usually much slower. Use `Promise.allSettled` when you need every result even if some operations fail.

JavaScript Security Best Practices

This is a practical, up-to-date guide to JavaScript Security — what it is, why it matters in 2026, and how to apply it in real projects. It is written for developers and founders who want clear answers and proven best practices, not filler.

Whether you're just starting out or leveling up, treat this as a working reference you can return to. Every section is built to be skimmed, applied, and shared.

How Do You Optimize JavaScript Performance?

The biggest wins come from doing less on the main thread, not from clever micro-optimizations. Profile first with the browser Performance panel or Lighthouse, find the long tasks, then attack them. Optimize for the metric users feel: Interaction to Next Paint should stay under 200 ms.

High-impact techniques:

Break long tasks into chunks and yield with scheduler.yield() or setTimeout.
Move CPU-heavy work to a Web Worker so the UI thread stays free.
Debounce or throttle high-frequency events like scroll, resize, and input.
Defer non-critical scripts and code-split large bundles.
Batch DOM reads and writes to avoid layout thrashing.

Measure again after each change; assumptions about hotspots are often wrong.

What Is a JavaScript Closure?

A closure is created every time a function is defined: the function keeps a live reference to the variables in the scope where it was declared, not where it is called. Because the inner function holds that reference, those variables survive after the outer function has returned. This is the mechanism behind data privacy, function factories, and stable callbacks.

A practical example is a counter:

function makeCounter() {
  let count = 0;
  return () => ++count;
}
const next = makeCounter();
next(); // 1
next(); // 2

The returned arrow function closes over count. Each makeCounter() call produces an independent count, so two counters never interfere. Closures are not copies of values; they share the actual binding, which is why loop variables declared with var historically caused surprises that let fixes.

What Is the Difference Between Microtasks and Macrotasks?

Macrotasks include setTimeout, setInterval, message events, and I/O callbacks. Microtasks include promise .then/.catch/.finally reactions, queueMicrotask, and await continuations. The defining rule: after each macrotask, the engine drains the microtask queue completely before the next macrotask or paint.

Microtasks have higher priority and can starve rendering if you enqueue them in an unbounded loop.
One setTimeout(fn, 0) waits for the next macrotask turn, so it always runs after pending promises.
await splits a function: code after it resumes as a microtask.

Knowing this prevents subtle bugs where state appears to update in the wrong order, and explains why heavy promise chains can delay visual updates.

What Are the Core Advanced JavaScript Concepts to Master?

Beyond syntax, a handful of concepts unlock the language. The prototype chain explains inheritance: objects delegate property lookups to their prototype, and class is sugar over this mechanism. Lexical scope and closures explain how state is captured. The event loop explains concurrency without threads.

A practical study list:

Closures, scope, and the module pattern.
The prototype chain and class semantics.
The event loop, microtasks, and async/await.
Immutability, pure functions, and avoiding shared mutable state.
ES modules, tree shaking, and dynamic import().

These ideas reinforce one another. Understanding the event loop, for instance, makes promises, performance tuning, and debugging async ordering far more intuitive than memorizing rules in isolation.

What Causes Memory Leaks in JavaScript?

JavaScript is garbage collected, but objects are only freed when nothing references them. Leaks happen when references outlive their usefulness, so the collector cannot reclaim memory. Over time this grows the heap and degrades performance, especially in long-lived single-page apps.

Common culprits:

Timers and intervals that are never cleared.
Event listeners left attached to removed elements.
Detached DOM nodes still referenced by JavaScript variables.
Caches, maps, and arrays that grow without bound.
Closures that unintentionally retain large objects.

Use the DevTools Memory panel and heap snapshots to find retained objects, and prefer WeakMap/WeakSet for associations that should not prevent collection. Always pair addEventListener and setInterval with their cleanup.

When Should You Use Promises vs Callbacks?

Callbacks are still appropriate for simple, synchronous-style APIs and for event handlers that fire many times. For one-shot asynchronous results, promises and async/await are almost always the better choice: they flatten nesting, propagate errors predictably, and compose with combinators.

Promises shine when coordinating multiple operations:

Promise.all waits for everything and rejects fast on the first failure.
Promise.allSettled waits for all results regardless of failures.
Promise.race resolves with the first settled promise.
Promise.any resolves with the first success, ignoring rejections.

The classic "callback hell" of deeply nested handlers disappears once you return promises and chain or await them. Mixing both styles in one flow, however, is a frequent source of swallowed errors.

JavaScript Security: Key Facts and Data

According to recent industry research and the official documentation linked below:

Interaction to Next Paint (INP) targets a response under 200 ms to be rated good in Core Web Vitals
ECMAScript is updated annually, with ES2025 being the edition ratified in June 2025 by Ecma International
Stack Overflow's 2024 Developer Survey ranked JavaScript among the most commonly used languages, used by about 62% of developers

Quick-Reference Summary

A map of what this guide covers:

Topic	What you'll learn
How Do You Optimize JavaScript Performance?	The biggest wins come from doing less on the main thread, not from clever micro-optimizations.
What Is a JavaScript Closure?	A closure is created every time a function is defined
What Is the Difference Between Microtasks and Macrotasks?	Macrotasks include setTimeout, setInterval, message events, and I/O callbacks.
What Are the Core Advanced JavaScript Concepts to Master?	Beyond syntax, a handful of concepts unlock the language.
What Causes Memory Leaks in JavaScript?	JavaScript is garbage collected, but objects are only freed when nothing references them.
When Should You Use Promises vs Callbacks?	Callbacks are still appropriate for simple, synchronous-style APIs and for event handlers that fire many times.

How to Get Started with JavaScript Security

A simple path that works:

Learn the fundamentals of JavaScript Security from primary sources, not just tutorials.
Build one small, real project end to end.
Get feedback, refactor, and add tests.
Ship it publicly and document what you learned.
Repeat with a slightly harder project each time.

Build It with a World-Class Full Stack Developer

Sandeep Kumar Chaudhary is a full stack world-class developer. If you want to turn this into a real, production-ready product, get in touch — message directly on WhatsApp at +9779802348957 for a fast, no-pressure consult.

You can also explore the projects already shipped to thousands of users, or start a conversation here.

Final Thoughts

A closure is a function bundled with references to its surrounding lexical scope, letting it remember variables after the outer function returns. The developers and teams who win in 2026 pair strong fundamentals with consistent shipping. Start small, stay curious, build in public, and revisit this guide as your skills grow.