Why use Map in JavaScript for key-value pairs

Why I reach for Map in JavaScript (and you should too) If you're still using plain objects for every key-value need, try Map next time — especially when your keys aren’t simple strings or when performance and predictable iteration order matter. // Quick JavaScript Map example const users = new Map(); // set users.set(1, { name: "Asha", role: "Designer" }); users.set(2, { name: "Ravi", role: "Developer" }); // get console.log(users.get(1)); // { name: "Asha", role: "Designer" } // size, has, delete console.log(users.size); // 2 console.log(users.has(2)); // true users.delete(2); // iterate for (const [id, user] of users) { console.log(id, user.name); } // convert to array const arr = Array.from(users.entries()); When to choose Map: 1. Keys can be anything (objects, functions, primitives). 2. You need guaranteed insertion order during iteration. 3. You want faster operations for frequent add/remove compared to large-object hacks. Pro tip: Use Map for caches, metadata stores, or when keys are non-string references. For simple JSON-like data or when you need JSON.stringify, stick with plain objects. Have you used Map in a real project? What problem did it solve for you? 👇 #javascript #webdev #frontend #programming #codingtips

  • No alternative text description for this image

To view or add a comment, sign in

Explore content categories