# Understanding JavaScript Closures Through Call Stack, Heap Memory & `[[Scopes]]`

Jun 26, 2026 · 6:27 AM UTC ·4 min read · 0 reactions · 0 comments · 31 views

#javascript #closures #callstack #Gaurav Singh #JavaScript #Heap Memory

TL;DR · WeSearch summary

The article discusses JavaScript closures, explaining how they work and what happens behind the scenes. It describes the role of the call stack and heap memory in storing variables and how closures preserve the lexical environment. The article provides examples and visualizations to help illustrate the process of creating and using closures.

Key facts

▪Closures are a way for JavaScript to keep data alive when a function still needs it.
▪The call stack and heap memory are two important memory areas involved in the execution of functions.
▪Closures preserve the lexical environment, allowing variables to survive after a function finishes executing.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/gauravsingh7x/-understanding-javascript-closures-through-call-stack-heap-memory-scopes-5gha
Publication time	Fri, 26 Jun 2026 06:27:39 +0000
Retrieval time	2026-06-26T06:37:29.198Z
Last seen	2026-06-26T06:37:29.198Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	ga31JCmWJXyc
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3943940) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Gaurav Singh Posted on Jun 26 # Understanding JavaScript Closures Through Call Stack, Heap Memory & `[[Scopes]]` #javascript #closure #callstack #heapmemory Closures aren't magic—they're simply JavaScript's way of keeping data alive when a function still needs it. Every JavaScript developer has heard statements like: "A closure is a function that remembers variables from its outer scope." "The inner function closes over variables." "Closures preserve the lexical environment." But...

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments