JavaScript data types and data structures

JavaScript is a dynamic types. Variables in JavaScript are not directly associated with any particular value type, and any variable can be assigned (and re-assigned) values of all types:

let foo = 42; / foo is now a number
foo = "bar"; / foo is now a string
foo = true; / foo is now a boolean

JavaScript is also a weakly typed language, which means it allows implicit type conversion when an operation involves mismatched types, instead of throwing type errors.

const foo = 42; / foo is a number
const result = foo + "1"; / JavaScript coerces foo to a string, so it can be concatenated with the other operand
console.log(result); / 421

Implicit coercions are very convenient, but can create subtle bugs when conversions happen where they are not expected, or where they are expected to happen in the other direction (for example, string to number instead of number to string). For symbols and BigInts, JavaScript has intentionally disallowed certain implicit type conversions.

All types except Object define immutable values represented directly at the lowest level of the language. We refer to values of these types as primitive values.

All primitive types, except typeof operator. typeof null returns "object", so one has to use === null to test for null.

All primitive types, except toExponential(). When a property is accessed on a primitive value, JavaScript automatically wraps the value into the corresponding wrapper object and accesses the property on the object instead. However, accessing a property on null or undefined throws a TypeError exception, which necessitates the introduction of the optional chaining operator.

The object wrapper classes' reference pages contain more information about the methods and properties available for each type, as well as detailed descriptions for the semantics of the primitive types themselves.

The Null type is inhabited by exactly one value: undefined.

Conceptually, undefined indicates the absence of a value, while null indicates the absence of an object (which could also make up an excuse for typeof null === "object"). The language usually defaults to undefined when something is devoid of a value:

• A return statement with no value (return;) implicitly returns undefined.
• Accessing a nonexistent object property (obj.iDontExist) returns undefined.
• A variable declaration without initialization (let x;) implicitly initializes the variable to undefined.
• Many methods, such as Map.prototype.get(), return undefined when no element is found.

null is used much less often in the core language. The most important place is the end of the Object.create(), etc., accept or return null instead of undefined.

null is a Boolean type represents a logical entity and is inhabited by two values: true and false.

Boolean values are usually used for conditional operations, including Number type is a Number.MIN_SAFE_INTEGER) to 2⁵³ − 1 (Number.isSafeInteger().

Values outside the representable range are automatically converted:

• Positive values greater than Number.MAX_VALUE are converted to Infinity.
• Positive values smaller than Number.MIN_VALUE are converted to 0.
• Negative values smaller than -Number.MAX_VALUE are converted to -Infinity.
• Negative values greater than -Number.MIN_VALUE are converted to -0.

Infinity and -Infinity behave similarly to mathematical infinity, but with some slight differences; see Number.NEGATIVE_INFINITY for details.

The Number type has only one value with multiple representations: 0 is represented as both -0 and +0 (where 0 is an alias for +0). In practice, there is almost no difference between the different representations; for example, +0 === -0 is true. However, you are able to notice this when you divide by zero:

console.log(42 / +0); / Infinity
console.log(42 / -0); / -Infinity

NaN ("Not a Number") is a special kind of number value that's typically encountered when the result of an arithmetic operation cannot be expressed as a number. It is also the only value in JavaScript that is not equal to itself.

Although a number is conceptually a "mathematical value" and is always implicitly floating-point-encoded, JavaScript provides bitwise operators. When applying bitwise operators, the number is first converted to a 32-bit integer.

It may be necessary to use such techniques in very constrained environments, like when trying to cope with the limitations of local storage, or in extreme cases (such as when each bit over the network counts). This technique should only be considered when it is the last measure that can be taken to optimize size.

The Number.MAX_SAFE_INTEGER) for Numbers.

A BigInt is created by appending n to the end of an integer or by calling the BigInt() function.

This example demonstrates where incrementing the Number.MAX_SAFE_INTEGER returns the expected result:

/ BigInt
const x = BigInt(Number.MAX_SAFE_INTEGER); / 9007199254740991n
x + 1n === x + 2n; / false because 9007199254740992n and 9007199254740993n are unequal

/ Number
Number.MAX_SAFE_INTEGER + 1 === Number.MAX_SAFE_INTEGER + 2; / true because both are 9007199254740992

You can use most operators to work with BigInts, including +, *, -, **, and % — the only forbidden one is loosely so.

BigInt values are neither always more precise nor always less precise than numbers, since BigInts cannot represent fractional numbers, but can represent big integers more accurately. Neither type entails the other, and they are not mutually substitutable. A UTF-16 code units. Each element in the string occupies a position in the string. The first element is at index 0, the next at index 1, and so on. The String reference page for more details.

JavaScript strings are immutable. This means that once a string is created, it is not possible to modify it. String methods create new strings based on the content of the current string — for example:

• A substring of the original using substring().
• A concatenation of two strings using the concatenation operator (+) or concat().

Beware of "stringly-typing" your code!

It can be tempting to use strings to represent complex data. Doing this comes with short-term benefits:

• It is easy to build complex strings with concatenation.
• Strings are easy to debug (what you see printed is always what is in the string).
• Strings are the common denominator of a lot of APIs (Response.text(), etc.) and it can be tempting to only work with strings.

With conventions, it is possible to represent any data structure in a string. This does not make it a good idea. For instance, with a separator, one could emulate a list (while a JavaScript array would be more suitable). Unfortunately, when the separator is used in one of the "list" elements, then, the list is broken. An escape character can be chosen, etc. All of this requires conventions and creates an unnecessary maintenance burden.

Use strings for textual data. When representing complex data, parse strings, and use the appropriate abstraction.

A Functions are, in fact, also objects with the additional capability of being callable.

In JavaScript, objects can be seen as a collection of properties. With the object literal syntax, a limited set of properties are initialized; then properties can be added and removed. Object properties are equivalent to key-value pairs. Property keys are either strings or symbols. When other types (such as numbers) are used to index objects, the values are implicitly converted to strings. Property values can be values of any type, including other objects, which enables building complex data structures.

There are two types of object properties: The data property and the accessor property. Each property has corresponding attributes. Each attribute is accessed internally by the JavaScript engine, but you can set them through Object.defineProperty() page.

Data property

Data properties associate a key with a value. It can be described by the following attributes:

value

The value retrieved by a get access of the property. Can be any JavaScript value.

writable

A boolean value indicating if the property can be changed with an assignment.

enumerable

A boolean value indicating if the property can be enumerated by a Enumerability and ownership of properties for how enumerability interacts with other functions and syntaxes.

configurable

A boolean value indicating if the property can be deleted, can be changed to an accessor property, and can have its attributes changed.

Accessor property

Associates a key with one of two accessor functions (get and set) to retrieve or store a value.

An accessor property has the following attributes:

get

A function called with an empty argument list to retrieve the property value whenever a get access to the value is performed. See also getters. May be undefined.

set

A function called with an argument that contains the assigned value. Executed whenever a specified property is attempted to be changed. See also setters. May be undefined.

enumerable

A boolean value indicating if the property can be enumerated by a Enumerability and ownership of properties for how enumerability interacts with other functions and syntaxes.

configurable

A boolean value indicating if the property can be deleted, can be changed to a data property, and can have its attributes changed.

The prototype of an object points to another object or to null — it's conceptually a hidden property of the object, commonly represented as [[Prototype]]. Properties of the object's [[Prototype]] can also be accessed on the object itself.

Objects are ad-hoc key-value pairs, so they are often used as maps. However, there can be ergonomics, security, and performance issues. Use a Temporal object. Date has many undesirable design choices and should be avoided in new code if possible.

Arrays are regular objects for which there is a particular relationship between integer-keyed properties and the length property.

Additionally, arrays inherit from Array.prototype, which provides a handful of convenient methods to manipulate arrays. For example, push() appends an element to the array. This makes Arrays a perfect candidate to represent ordered lists.

DataView.

These data structures take object references as keys. WeakMap represent a collection of key-value associations.

You could implement Maps and Sets yourself. However, since objects cannot be compared (in the sense of < "less than", for instance), neither does the engine expose its hash function for objects, look-up performance would necessarily be linear. Native implementations of them (including WeakMaps) can have look-up performance that is approximately logarithmic to constant time.

Usually, to bind data to a DOM node, one could set properties directly on the object, or use data-* attributes. This has the downside that the data is available to any script running in the same context. Maps and WeakMaps make it easy to privately bind data to an object.

WeakMap and WeakSet only allow garbage-collectable values as keys, which are either objects or reference to find out more about the built-in objects.

As mentioned above, JavaScript is a weakly typed language. This means that you can often use a value of one type where another type is expected, and the language will convert it to the right type for you. To do so, JavaScript defines a handful of coercion rules.

The primitive coercion process is used where a primitive value is expected, but there's no strong preference for what the actual type should be. This is usually when a string, a number, or a BigInt are equally acceptable. For example:

• The Date() constructor, when it receives one argument that's not a Date instance — strings represent date strings, while numbers represent timestamps.
• The + operator — if one operand is a string, string concatenation is performed; otherwise, numeric addition is performed.
• The == operator — if one operand is a primitive while the other is an object, the object is converted to a primitive value with no preferred type.

This operation does not do any conversion if the value is already a primitive. Objects are converted to primitives by calling its string coercion.

The [Symbol.toPrimitive]() method, if present, must return a primitive — returning an object results in a TypeError is thrown. For example, in the following code:

console.log({} + []); / "[object Object]"

Neither {} nor [] have a [Symbol.toPrimitive]() method. Both {} and [] inherit valueOf() from [].toString() returns "", so the result is their concatenation: "[object Object]".

The [Symbol.toPrimitive]() method always takes precedence when doing conversion to any primitive type. Primitive conversion generally behaves like number conversion, because valueOf() is called in priority; however, objects with custom [Symbol.toPrimitive]() methods can choose to return any primitive. Symbol.prototype[Symbol.toPrimitive]() ignores the hint and always returns a symbol.

There are two numeric types: Number and BigInt. Sometimes the language specifically expects a number or a BigInt (such as BigInt coercion.

Numeric coercion is nearly the same as string coercion, object coercion for more details.

As you may have noticed, there are three distinct paths through which objects may be converted to primitives:

• Primitive coercion: [Symbol.toPrimitive]("default") → valueOf() → toString()
• Numeric coercion, BigInt coercion: [Symbol.toPrimitive]("number") → valueOf() → toString()
• String coercion: [Symbol.toPrimitive]("string") → toString() → valueOf()

In all cases, [Symbol.toPrimitive](), if present, must be callable and return a primitive, while valueOf or toString will be ignored if they are not callable or return an object. At the end of the process, if successful, the result is guaranteed to be a primitive. The resulting primitive is then subject to further coercions depending on the context.

• JavaScript Data Structures and Algorithms by Oleksii Trekhleb
• Computer Science in JavaScript by Nicholas C. Zakas