What is explicit resource management?

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. This guide covers explicit resource management end to end — core concepts, best practices, concrete data, and a step-by-step approach you can apply right away.

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 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.

Should I use ES modules or CommonJS?

Prefer ES modules for new code. They are the language standard, use static `import`/`export` that enables tree shaking and smaller bundles, support top-level `await`, and run natively in browsers and modern Node.js. CommonJS with `require` is still common in older Node projects, but ESM is the forward-looking default.

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.

How Explicit Resource Management With the using Keyword Works Under the Hood

This is a practical, up-to-date guide to Explicit Resource Management — 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.

Why Does My Async Code Run in an Unexpected Order?

Most ordering confusion comes from forgetting that await yields control. Everything before the first await runs synchronously; everything after resumes later as a microtask. Meanwhile, synchronous code that called the async function keeps executing first.

Consider:

console.log('A');
(async () => {
  console.log('B');
  await null;
  console.log('D');
})();
console.log('C');

The output is A B C D. B runs synchronously, the function suspends at await, C runs, then the microtask resumes with D. Mapping out which lines run before and after each await resolves nearly all of these surprises without a debugger.

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.

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 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.

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.

How Does the JavaScript Event Loop Work?

JavaScript runs on a single thread with a call stack, a task (macrotask) queue, and a microtask queue. The engine takes one task, runs it to completion, then empties the entire microtask queue before doing anything else. Only after microtasks drain does the browser get a chance to render and pick the next task.

The ordering matters in practice:

Synchronous code on the call stack runs first.
Promise reactions and queueMicrotask callbacks run next, fully draining.
Timers, I/O, and events run as later macrotasks.

This is why a Promise.resolve().then(...) always fires before a setTimeout(..., 0). Long synchronous work blocks the loop entirely, freezing input and rendering, which is the root cause of jank.

Explicit Resource Management: Key Facts and Data

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

V8 powers Chrome, Node.js, Deno, and Edge, compiling JavaScript to machine code with its TurboFan and Maglev optimizing compilers
Interaction to Next Paint (INP) targets a response under 200 ms to be rated good in Core Web Vitals
Microtasks such as Promise callbacks drain completely after each task and before the next render, giving them priority over setTimeout callbacks

Quick-Reference Summary

A map of what this guide covers:

Topic	What you'll learn
Why Does My Async Code Run in an Unexpected Order?	Most ordering confusion comes from forgetting that await yields control.
What Causes Memory Leaks in JavaScript?	JavaScript is garbage collected, but objects are only freed when nothing references them.
What Is the Difference Between Microtasks and Macrotasks?	Macrotasks include setTimeout, setInterval, message events, and I/O callbacks.
What Is a JavaScript Closure?	A closure is created every time a function is defined
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 Does the JavaScript Event Loop Work?	JavaScript runs on a single thread with a call stack, a task (macrotask) queue, and a microtask queue.

How to Get Started with Explicit Resource Management

A simple path that works:

Learn the fundamentals of Explicit Resource Management 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

Most JavaScript performance wins come from reducing main-thread work, not micro-optimizing tight loops. 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.