Over a million developers have joined DZone.

The First ECMAScript.next Features in Firefox and Chrome

DZone's Guide to

The First ECMAScript.next Features in Firefox and Chrome

· Web Dev Zone
Free Resource

Discover how to focus on operators for Reactive Programming and how they are essential to react to data in your application.  Brought to you in partnership with Wakanda

The next version of ECMAScript (code-named ECMAScript.next [1]) will be standardized by 2013. This post enumerates the first features that are currently being tested in Firefox and Chrome.


Dave Mandelin mentions Mozilla’s ES6 planning page. He points out the following highlights (paraphrasing an email of his):

The block-scoped let and const have been available in Firefox for a long time.

V8 (Chrome, Node.js)

A post on Google+ provides details on V8. Quoting François Beaufort:

A new flag named Enable Experimental JavaScript appeared in the chrome://flags page of the last Chromium build. This flag enables web pages to use experimental JavaScript features.

A code search suggested by Paul Irish shows the relevant flags:

DEFINE_bool(harmony_typeof, false, "enable harmony semantics for typeof")
DEFINE_bool(harmony_scoping, false, "enable harmony block scoping")
DEFINE_bool(harmony_proxies, false, "enable harmony proxies")
DEFINE_bool(harmony_collections, false,
            "enable harmony collections (sets, maps, and weak maps)")

Andreas Rossberg elaborates:

... the --harmony flag currently activates the following experimental features for V8: On the browser side, that should become functional in Chrome 17 (some of it is in 16 already, but incomplete/buggy) by setting
If you are on the Chrome dev channel, you should also see it show up on chrome://flags soon.

Related reading

  1. A brief history of ECMAScript versions (including Harmony and ES.next)
  2. ECMAScript.next: the “TXJS” update by Eich
  3. es6-shim – ECMAScript 6 functionality on ECMAScript 5


Source: http://www.2ality.com/2012/01/esnext-features.html

Learn how divergent branches can appear in your repository and how to better understand why they are called “branches".  Brought to you in partnership with Wakanda


Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}