DEV Community

Cover image for ES2020 Features in simple examples
Carlos Caballero
Carlos Caballero

Posted on • Originally published at

ES2020 Features in simple examples

In this series, we are going to show the EcmaScript features from 2015 to today.


ES2020 is the version of ECMAScript corresponding to the year 2020. This version does not include as many new features as those that appeared in ES6 (2015). However, some useful features have been incorporated.

This article introduces the features provided by ES2020 in easy code examples. In this way, you can quickly understand the new features without the need for a complex explanation.

Of course, it is necessary to have a basic knowledge of JavaScript to fully understand the best ones introduced.

The new #JavaScript features in ES2020 are:

➡️ String.prototype.matchAll
➡️ import()
➡️ BigInt
➡️ Promise.allSettled
➡️ globalThis
➡️ for-in mechanics
➡️ Optional Chaining
➡️ Nullish coalescing Operator


The matchAll() method returns an iterator of all results matching a string against a regular expression, including capturing groups.

Dynamic import

Dynamic import() returns a promise for the module namespace object of the requested module. Therefore, imports can now be assigned to a variable using async/await.

BigInt — Arbitrary precision integers

BigInt is the 7th primitive type and It is an arbitrary-precision integer. The variables can now represent ²⁵³ numbers and not just max out at 9007199254740992.


Promise.allSettled returns a promise that is fulfilled with an array of promise state snapshots, but only after all the original promises have settled, i.e. become either fulfilled or rejected.

We say that a promise is settled if it is not pending, i.e. if it is either fulfilled or rejected.

Standardized globalThis object

The global this was not standardized before ES10.
In production code you would “standardize” it across multiple platforms on your own by writing this monstrosity:

for-in mechanics

ECMA-262 leaves the order of for (a in b)... almost totally unspecified, but real engines tend to be consistent in at least some cases.

Historical efforts to get consensus on a complete specification of the order of for-in have repeatedly failed, in part because all engines have their own idiosyncratic implementations which are the result of a great deal of work and which they don’t really want to revisit.

In conclusion, the different engines have agreed on how properties are iterated when using the for (a in b) control structure so that the behavior is standardized.

Nullish coalescing Operator

When performing property accesses, it is often desired to provide a default value if the result of that property access is null or undefined. At present, a typical way to express this intent in JavaScript is by using the || operator.

This works well for the common case of null and undefined values, but there are a number of falsy values that might produce surprising results.

The nullary coalescing operator is intended to handle these cases better and serves as an equality check against nullary values (null or undefined). If the expression at the left-hand side of the ?? operator evaluates to undefined or null, its right-hand side is returned.

Optional Chaining

When looking for a property value that’s deep in a tree-like structure, one often has to check whether intermediate nodes exist.

The Optional Chaining Operator allows handle many of those cases without repeating themselves and/or assigning intermediate results in temporary variables.

Also, many API return either an object or null/undefined, and one may want to extract a property from the result only when it is not null:

When some other value than undefined is desired for the missing case, this can usually be handled with the Nullish coalescing operator:


JavaScript is a live language, and that is something very healthy for web development. Since the appearance of ES6 in 2015 we are living a vibrant evolution in the language. In this post we have reviewed the features that arise in ES2020.

Although many of these features may not be essential for the development of your Web application, they are giving possibilities that could be achieved before with tricks or a lot of verbosity.

Top comments (11)

pavelloz profile image
Paweł Kowalski

Although many of these features may not be essential for the development of your Web application, they are giving possibilities that could be achieved before with tricks or a lot of verbosity.

Yea, constant legacy worrying and xbrowser issues push me further and further away from the frontend. Nodejs is far more comfortable and user friendly environment than whatever google next patch will bring, safari wont support or client with ie11 will complain ;)

balaji1202 profile image
Balaji Saravanan

Why don't you try a transpiler?

pavelloz profile image
Paweł Kowalski

I use transpiler. That doesnt save you from different implementations of features in different browsers.

calvinmills profile image
Calvin Mills

Thanks for taking the time to put this together, great high level summary of some exciting upcoming features!

carlillo profile image
Carlos Caballero

Thanks Calvin!

I hope to complete the series although ES6 has already been written enough. However, the ideal is to have a place where the news that the standard brings us annually is summarized and updated.

freekvanrijt profile image
Freek van Rijt

Thanks for the write-up! Any word about browser adoption of these features?

Either way, they should be in core-js / babel soon, which will help a lot (especially a fan of using optional chaining 🥳)

deciduously profile image
Ben Lovy

I keep this compatibility table bookmarked.

patarapolw profile image
Pacharapol Withayasakpunt

Finally, ??. I hope with works fine just like ?. in TypeScript.

Can I use this in esnext?

douglasdgmarques profile image
Douglas Marques

Nice article, thank you for the explanations.

abhishekdeshmukh74 profile image
Abhishek Deshmukh

I have written an in-depth blog post on the same topic
Feel free to check it out

markkupainomaa profile image

In Nullish section falsy examples:

const value = values.numberValue || 300; //300

I think you wrote values.numberValue instead of values.zeroValue? Because it's supposed to return 400.