Skip to content

Instantly share code, notes, and snippets.

What would you like to do?

Javascript 2019 - ES10 New Features

It is 2019, and there is a bunch of new features that got approved by the TC49 consortium and soon will become part of ES10 standard.

My name is Maksim and let's check them out.

One thing before we move to the code examples: watch this video till the end, because I'll show you how to always well informed and up to date about new Javascript features.


First thing we're gonna look at is Array.flat method.

What it does is it flattens the array by given depth.

If you used Lodash or Underscore - you are already familiar with this method. It is called flatten or flattenDepth there.

Let's look at an example.

const fruits = [[πŸ‹, 🍌], [🍎, 🍏], [🍐, πŸ‘]];

const flatFruits = friuts.flat(); // Default flat level is 1

// [πŸ‹, 🍌, 🍎, 🍏, 🍐, πŸ‘];

I think it's great that we've got this method, so now we don't have to use external libraries or white our own wordy solutions for this simple task.


Moving on, another thing you can do with arrays now is that you call the flatMap method on them.

As you can guess by it's name this method combines flat and map methods and allows you to map through the array of items and then flatten the result in one go.

const fruits = [πŸ‹, 🍌, 🍎, 🍏, 🍐, πŸ‘];
const fruitNames = ['Lemon', 'Banana', 'Red Apple', 'Green Apple', 'Pear', 'Peach']

const mappedExample =, index) => [fruit, fruitNames[index]]);

const mappedAndFlattenedExample = fruits.flatMap((fruit, index) => [fruit, fruitNames[index]]);

Here we have an array of fruits from previous example, let's provide a second array with those fruits names.

Now let's say that we want to combine those arrays so after each fruit emoji we'll have this fruit name.

To do this we map through the fruits array with index and for each fruit we return an array combining fruit and fruit name with same index.

If we log it we'll see that we got a two dimentional array of fruits and their names.

Let's change map to flatMap - now we get a regular one dimentional array of fruits with their names.


String prototype also got some updates, now we can trim whitespaces from beginning or end of our string using trimLeft / trimRight methors:

const untrimmedString = "     Trim me 😒    ";


Here we have an untrimmed string with a bunch of whitespaces in the beginning and end. We can easily trim either of them using trimLeft or trimRight methods.


Object now has fromEntries method. Now you can take an array of entries:

const fruitEntries = [
  ["πŸ‹", "Lemon"],
  ["🍌", "Banana"],
  ["🍎", "Red Apple"],
  ["🍏", "Green Apple"],
  ["🍐", "Pear"],
  ["πŸ‘", "Peach"]

const fruitsObject = Object.fromEntries(fruitEntries);

And create an object from it. Previously we had only the Object.entries which would take and object and return an array of [key, value] pairs.

Optional Catch Binding

Next goes ability to not bind the parameter to the catch clause:

try {
  throw "Error we don't care about";
} catch (error) {
  // Some handling logic

So if you don't need that error parameter you can just omit it.

try {
  throw "Error we don't care about";
} catch {
  // Some handling logic

I have to note that it's quite controversial, and you might want to read an extensive article by Axel Rauschmayer where he talks about implications of this method and some alternatives.

It's a good read - so check it out.

Function toString Revision

Function toString method was reviewed. In ES6 when toString was invoked on a function it would return string representation of that function depending on ECMAScript engine.

When possible it would return the source code, otherwise - a standartized placeholder. So if toString couldn't create syntactically valid Javascript code, it would return a string for which eval throws a SyntaxError. It was a requirement so that eval couldn't parse this string.

Problem with that was that you could never be 100% sure that a future version of ECMAScript won't make it syntactically valid.

New proposal standardizes the placeholder: a function with body { [native code] }.

Let's look at examples:

For functions defined with Javascript code toString will return their original source code:

function exampleFuncton() {
  // Hello, I'm an ordinary function


Built-in function objects, bound function exotic objects and callable objects not defined in Javascript code will return a NativeFunction string:

// function isNaN() { [native code] }

// function pow() { [native code] }

console.log(function foo() {}.bind(null).toString());
// function () { [native code] }

If a function is a [well-known intrinsic object][] (Array, Error, isNan, etc) then the initial value of its name will appear in the result.

Symbol Description Accessor

Update for symbols!

When you create a symbol you can provide a string as a description:

const symbolExample = Symbol("Symbol description");

Previously you would have to call toString on it to get the description:

const symbolExample = Symbol("Symbol description");
// 'Symbol(Symbol description)'

Now we have a getter to access Symbol description:

const symbolExample = Symbol("Symbol description");
// Symbol description

Looks much cleaner, right?

How To Track New Js Features

Now as I've promised you in the beginning - how to keep up to date with new Javascript features.

Track the TC39 proposals repository. TC39 is a commettee that eveolves Javascript.

In that repo you'll find documents describing proposals on 4 stages:

  • Stage 0 - Strawman Those are either yet to be presented to the committee or presented but not yet achieved criteria to get into stage 1. Strawman proposals don't have any criteria.
  • Stage 1 - Proposal This is a stage when proposal stops being a strawman and starts to shape as something that might potentially become a javascript feature. It needs to have some illustrative examples, and high-level API described. At this point proposal should have a "champion" assigned to it who will advance it's addition to standard.
  • Stage 2 - Draft Proposals at this stage should also get an initial spec text.
  • Stage 3 - Candidate Spec text should be completed, reviewed and approved.
  • Stage 4 - Finished If the proposal gets to this stage it means that it will be included in next edition of the formal ECMAScript standard.

Now just check out this repo from time to time, read the proposals and be on the bleeding edge of Javascript.

Now like this video, or dislike it, react anyhow. Give me comments and have a good day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment