8 new JavaScript features you might have missed

The JavaScript juggernaut never ever stops. There are a selection of characteristics introduced by the “living spec” every single year. Then it will take some time for the browsers, Node.js, etcetera. to roll them in, and in advance of you know it, there’s a huge pile of new JavaScript features you haven’t tried using.

It is not way too late. Here I have rounded up the ES11 (ECMAScript 11, aka ECMAScript 2020) features that you may perhaps have skipped. They include a number of ergonomic and other modern enhancements. Let’s just take a glance.

Optional chaining

Optional chaining is one of these basic-but-helpful niceties that just will make existence a minor a lot easier. This attribute allows you to navigate object and operate chains with a shorthand for dealing with null or undefined values. 

Optional chaining is effective for uncomplicated conditions like nested object details, for capabilities that return non-existent values, and even for functions that don’t exist as member procedures on objects. So you can do issues like we see in Listing 1. 

Listing 1. Optional chaining examples

box = 
  innerBox: ,
  nullFunction: purpose() return null ,
  // non-existent method foo() and customers bar

// with optional chaining:
if (box?.innerBox?.foo) // navigate object graph safely
// outdated model without the need of optional chaining:
if (box.innerBox && box.innerBox.foo)
//also functions for capabilities:
// and nonexistent approaches and members:
box?.foo() && box?.bar

The code is additional concise in expressing just what you want: If the point exists, navigate to it if not, return undefined.


An additional sensible addition to the main language, globalThis, is an abstraction of the international object available to the present-day context. The most very well-acknowledged and ancient of these is the window item discovered in JavaScript working in the browser. But environments like Node.js and internet staff have their individual root objects that provide precisely the exact same objective: global and self, respectively.

globalThis will make code that is extra moveable (and gets rid of existence checks) by wrapping all of these root objects in the a single identifier that resolves to the world-wide root item in whichever setting the code is executing in.


Right before ES11 the biggest integer that could be referenced in JavaScript safely was Number.MAX_Secure_INTEGER, which resolves to 9007199254740991 (aka 2^53 – 1).  This might not be a each day trouble for some of us, but for quite a few apps it’s an amusingly small magnitude requiring programmers to use a wrapper like massive-integer.  (Observe that the huge-integer library is however beneficial as a polyfill.)

When making use of the common Range type to stand for such substantial figures, you will encounter unanticipated rounding. (See these reviews all utilize to pretty small numbers as very well, i.e. -2^53 – 1).

With ES11, the BigInt style is created in for these eventualities. You can determine it by adding an n to the stop of a number, as in mySafeBigNumber = 9007199254740992n.

This is genuinely a new form, not just some sleight of hand around the current Selection form. If you do typeof 12, you get range.  If you do typeof mySafeBigNumber, you get bigint. Moreover, if you try out just about anything nefarious like mySafeBigNumber - 12, you will get an mistake: “Cannot combine BigInt and other kinds, use explicit conversions.”

To transform amongst the two, you can use the constructors. For case in point, you could generate allow myUnsfeBigNumber = Variety(mySafeBigNumber), but wait around — you should not do that mainly because you just developed an unsafely big Variety item. So alternatively, only transform when the BigInt has been lowered to lesser than the MAX_Risk-free_INTEGER value.

In a identical vein, it is value pointing out that comparing Figures and BigInts for equality will constantly return wrong, given that they are diverse types.

BigInt also supports illustration in binary, oct, and hex notation and supports all the usual math operators you may well be expecting apart from the unary additionally operator, whose objective is to transform a worth to a Variety. The motive for this is relatively obscure, in keeping away from breaking improvements to present non-JS asm code.

At last, it may well feel redundant to level out, due to the fact it’s in the quite name, but BigInt represents integers. Managing the code x = 3n x = x / 2n will consequence in a benefit of 1n for x. BigInts quietly dispose of the fractional aspect of quantities.

Nullish coalescing

Nullish coalescing is the most poetically named of the ES11 capabilities, and joins optional chaining in aiding us in our dealings with nullish values. Nullish coalescing is also a new symbol, the double concern mark: ??. It is a rational operator with very similar behavior to the sensible OR operator (the double pipe image ||).

The variance in between ?? and || is in how the operator handles nullish as opposed to falsy values. Most JavaScript developers are acquainted with how the language treats non-boolean values when tests them as correct/untrue (in limited, wrong, , null, vacant strings, and undefined are regarded untrue and anything else resolves to genuine more aspects below). We’ll frequently get gain of this to examination for the existence of a thing and if it does not exist, then use a little something else, like so:

enable meaningOfLife = respond to || 42

This permits for environment a sort of default though swiftly tests for the existence of one thing in answer. That operates great if we actually want the meaningOfLife to default to 42 if any of the falsy values are set on response. But what if you only want to tumble back again to 42 if there is an precise nullish price (null or undefined, exclusively)?

?? tends to make that basic. You use

allow meaningOfLife = answer ?? 42

To make this very clear, feel about setting as the value on remedy, and how assigning a benefit to meaningOfLife would perform utilizing || vs ?? as in Listing 2. In this circumstance, we want to hold as the value if it is established, but use 42 if reply is in fact vacant.

Listing 2. Nullish coalescing in motion

permit remedy = 
let meaningOfLife = solution ?? 42 // meaningOfLife === - what we want
permit meaningOfLife = remedy || 42 // meaningOfLife === 42 - not what we want
enable remedy = undefined
let meaningOfLife = reply ?? 42 // meaningOfLife === 42 - what we want
let meaningOfLife = reply || 42 // meaningOfLife === 42 - also what we want


The ES11 spec adds a new system to the String prototype: matchAll. This strategy applies a standard expression to the String occasion and returns an iterator with all the hits. For case in point, say you needed to scan a string for all the sites exactly where a word commenced with t or T. You can do that as in Listing 3.

Listing 3. Making use of matchAll

allow textual content = "The best time to plant a tree was 20 several years ago. The 2nd ideal time is now."
let regex = /(?:^|s)(t[a-z0-9]w*)/gi // matches words and phrases commencing with t, case insensitive
let result = textual content.matchAll(regex)
for (match of consequence)

Established aside the inherent density of regex syntax and acknowledge that the regular expression defined in Listing 3 will obtain text commencing with t or T. matchAll() applies that regex to the string and gives you back again an iterator that lets you simply just and easily wander in excess of the benefits and entry the matching groups.

Dynamic imports

ES11 introduces an progression in how you can import modules, by allowing for arbitrary placement of imports that are loaded asynchronously. This is also identified as code splitting, anything we have been carrying out via create applications for decades now. Dynamic imports is an additional instance of the spec catching up with in-the-wild methods.

A basic instance of the syntax is revealed in Listing 4.

Listing 4. Async module import

allow asyncModule = await import('/lib/my-module.ts')

This form of import can look anyplace in your JS code, which include as a reaction to user situations. It makes it easy to lazy-load modules only when they are in fact wanted.


The promise.allSettled() system allows you to observe the effects of a established of promises no matter if they are fulfilled or rejected. This can be contrasted to guarantee.all(), which will conclude with a rejected guarantee or mistake non-guarantee. guarantee.allSettled() returns an array of objects describing the effects of each promise.

This is beneficial when viewing a group of unrelated promises. That is, you want to know what transpired to them all, even if some in the middle fail. Listing 5 has an illustration.

Listing 5. assure.allSettled() example

let guarantee1 = Assure.solve("Alright")
permit promise2 = Assure.reject("Not Ok")
allow promise3 = Assure.solve("Right after not alright")
Assure.allSettled([promise1, promise2, promise3])
    .then((final results) => console.log(outcomes))
    .catch((err) => console.log("error: " + err))

The catch lambda does not hearth in this scenario (it would if we experienced made use of assure.all).  Alternatively, the then clause executes, and an array with the contents of Listing 6 is returned. The vital takeaway here is that the 3rd assure has operate and we can see its final result even although promise2 unsuccessful in advance of it.

Listing 6. promise.allSettled() outcomes

  "status":"rejected","reason":"Not OK",
  "status":"fulfilled","value":"After not ok"

Export star syntax

This element provides the capability to export * from a module. You could currently import * from an additional module, but now you can export with the similar syntax, like Listing 7.

Listing 7. export * instance

Export * from '/dir/one more-module.js'

This is a sort of module chaining, enabling you to export all the things from yet another module from inside of the latest module. Valuable if you are developing a module that unites other modules into its API, for instance.

Standardization of for-in ordering

Did you know that the get of enumeration in excess of collections in for-in loops in JavaScript was not confirmed? Basically, it was assured by all JavaScript environments (browsers, Node.js, and so forth.), but now this de facto common has been absorbed by the spec. Idea imitates apply once again.

An evolving spec

A single of the most interesting matters about operating in the program market is watching the evolution of points. Programming languages are a single of the most essential expressions of all, the place a lot of the philosophy of pc science fulfills the reality of day-to-working day coding. JavaScript (like other residing languages) carries on to mature in response to these forces with its yearly release plan.

Copyright © 2022 IDG Communications, Inc.