A polyfill is code that adds a standard feature to an environment that doesn't have it yet, such as Promise.any or Array.prototype.flat in an older browser. It's written in plain JavaScript that the old environment can already run, and it follows the specification, the document that defines how the feature behaves, as closely as it can. Code written for new browsers then works in old ones too. The name comes from Polyfilla, a paste for filling cracks in walls: a polyfill fills the gaps in a browser.
A real polyfill checks for the feature first, as in if (!Promise.any), and defines it only when it's missing, so a browser that has the built-in keeps its own version:
if (!Array.prototype.flat) {
Array.prototype.flat = function flat(depth) {
// the steps the specification lists, written in plain JavaScript
};
}
Every array gets its methods from one shared object, Array.prototype, and every function from Function.prototype. So a method added there appears on every array or function in the program, even ones created before it was added, and inside it this is the array or function it was called on. Careful polyfills add it with Object.defineProperty rather than = as above, so that, like the built-ins, it isn't enumerable and doesn't show up in a for...in loop.
When an interviewer asks you to write a polyfill, they mean: reproduce a built-in's behaviour yourself, without calling it. It shows you know exactly what the built-in does, beyond its everyday use. The details are the point, because code written against the standard relies on them too:
| Built-in | Everyday use | Details a polyfill must match too |
|---|---|---|
Array.prototype.map | [1, 2].map((n) => n * 2) is [2, 4] | thisArg, holes, and the TypeError for a callback that isn't a function, thrown even when the array is empty |
Function.prototype.bind | A function with a fixed this | Preset arguments, and calling the result with new |
Promise.all | Waits for several promises | Plain values among them, an empty input, and an argument that isn't iterable |
Object.create | An object that inherits from the one you pass | null as the prototype, and a TypeError for one that's neither an object nor null |
JSON.stringify | Turns data into text | undefined and functions, toJSON, and a TypeError on cycles |
These tasks give your version its own name, such as Array.prototype.myMap, Object.myCreate, or JSON.myStringify, or make it a stand-alone function, such as promiseAll(iterable) or objectIs(a, b). Replacing the real method would change it for every other piece of code on the page, and leave you no built-in to compare yours with.
In production you rarely write polyfills by hand: libraries such as core-js provide them, and Babel can add the ones your target browsers need. A polyfill can only add missing objects, functions, and methods. New syntax, such as ?. or class, can't be added that way: a compiler has to rewrite it as older syntax, which is called transpiling.
An array's length counts slots, and a slot can be empty: no element at all, not even undefined. That empty slot is called a hole, and an array with holes is called sparse. Reading a hole gives undefined, the value you get for any property that doesn't exist, so it looks like an element holding undefined. Object.keys, which lists the indexes an array really has, tells the two apart:
const withHole = [1, , 3]; // nothing between the commas
const withUndefined = [1, undefined, 3];
withHole.length; // 3
withUndefined.length; // 3
withHole[1]; // undefined
withUndefined[1]; // undefined
Object.keys(withHole); // ["0", "2"]: there's no element at index 1
Object.keys(withUndefined); // ["0", "1", "2"]: there is one, and its value is undefined
Holes appear in a few ways:
| How | Example | Result |
|---|---|---|
| A gap in an array literal | [1, , 3] | A hole at index 1 |
new Array with one number | new Array(3) | Three holes, and length is 3 |
delete on an element | delete arr[1] | Index 1 becomes a hole, and length doesn't change |
| Writing past the end | arr[5] = 6 on [1, 2, 3] | Holes at indexes 3 and 4, and length is 6 |
Making length bigger | arr.length = 5 on [1, 2, 3] | Holes at indexes 3 and 4 |
Consoles mark holes so you can spot them: Chrome shows [1, , 3] as [1, empty, 3], and Node as [ 1, <1 empty item>, 3 ].
Built-in methods don't agree on what to do with a hole: some skip it, some keep it in their result, and some read it as undefined, or write null in JSON. That's why every task that rebuilds one of them says exactly what to do with holes. Here's [1, , 3] going through a few:
| Call | Result | What happened to the hole |
|---|---|---|
[1, , 3].filter(() => true) | [1, 3] | Skipped: the callback isn't called for it, and the result has no hole |
[1, , 3].map((n) => n * 10) | [10, , 30] | Skipped, but kept: the result has a hole in the same place |
[1, , 3].reduce((sum, n) => sum + n) | 4 | Skipped: 1 starts the total, and the callback runs once, to add 3 |
[1, , 3].flat() | [1, 3] | Dropped |
Array.from([1, , 3]) | [1, undefined, 3] | Read as undefined, which becomes a real element |
JSON.stringify([1, , 3]) | "[1,null,3]" | Written as null |
Write Array.prototype.myMap(callback, thisArg), which works like the built-in map without calling it. It returns a new array of the same length, where each element is callback(element, index, array), called with thisArg as its this. The original array doesn't change.
Match these details of the built-in. Holes (missing indexes, as in [1, , 3]) are skipped: the callback never sees them, and they stay holes in the result. The length is read once, before the loop, so elements pushed while it runs aren't visited. If callback isn't a function, throw a TypeError, even for an empty array.
[1, 2, 3].myMap((n) => n * 2); // [2, 4, 6]
[1, , 3].myMap((n) => n * 10); // [10, empty, 30]
["a", "b"].myMap(function (letter, index) {
return this.prefix + letter + index;
}, { prefix: "#" }); // ["#a0", "#b1"]
const numbers = [1, 2, 3];
const doubled = numbers.myMap((n) => n * 2);
expect(doubled).toEqual([2, 4, 6]);
expect(doubled).not.toBe(numbers);
expect(numbers).toEqual([1, 2, 3]);
const fn = spy();
const letters = ["a", "b"];
letters.myMap(fn);
expect(fn).toHaveBeenCalledTimes(2);
expect(fn).toHaveBeenCalledWith("a", 0, letters);
expect(fn).toHaveBeenCalledWith("b", 1, letters);
expect(fn.calls[1].args[2]).toBe(letters);
const context = { factor: 3 };
const result = [1, 2].myMap(function (n) {
return n * this.factor;
}, context);
expect(result).toEqual([3, 6]);
const fn = spy((n) => n * 10);
const result = [1, , 3].myMap(fn);
expect(fn).toHaveBeenCalledTimes(2);
expect(result).toHaveLength(3);
expect(1 in result).toBe(false);
expect(result).toEqual([10, , 30]);
const numbers = [1, 2];
const result = numbers.myMap((n) => {
if (numbers.length < 5) numbers.push(n * 10);
return n;
});
expect(result).toEqual([1, 2]);
expect(() => [1, 2].myMap("double")).toThrow(TypeError);
expect(() => [].myMap()).toThrow(TypeError);
const numbers = [1, 2];
const builtIn = Array.prototype.map;
// Only map on numbers throws, so other code, like console.log, still works.
Array.prototype.map = function (...args) {
if (this === numbers) throw new Error("myMap called the built-in map");
return builtIn.apply(this, args);
};
let result;
try {
result = numbers.myMap((n) => n + 1);
} finally {
Array.prototype.map = builtIn;
}
expect(result).toEqual([2, 3]);
Run tests runs every test on your code, here in your browser. The problem is solved when they all pass.
Ctrl + Enter runs the tests (⌘ + Enter on a Mac).
I'm here to help with Array.prototype.map. I give hints, never the solution, so you get to solve it yourself. Ask for a hint, select code to ask about it, or press Ask Tuto why on a failing test.
Your first 3 answers need no account. for free to keep asking.