All ECMAScript 2015 (ES6) features are split into three groups for shipping, staged, and in progress features:
- All shipping features, which V8 considers stable, are turned on by default on Node.js and do NOT require any kind of runtime flag.
- Staged features, which are almost-completed features that are not considered stable by the V8 team, require a runtime flag:
- In progress features can be activated individually by their respective harmony flag, although this is highly discouraged unless for testing purposes. Note: these flags are exposed by V8 and will potentially change without any deprecation notice.
The website node.green provides an excellent overview over supported ECMAScript features in various versions of Node.js, based on kangax's compat-table.
New features are constantly being added to the V8 engine. Generally speaking, expect them to land on a future Node.js release, although timing is unknown.
You may list all the in progress features available on each Node.js release by grepping through the
--v8-options argument. Please note that these are incomplete and possibly broken features of V8, so use them at your own risk:
node --v8-options | grep "in progress"
The V8 team is constantly working to improve the performance of new language features to eventually reach parity with their transpiled or native counterparts in EcmaScript 5 and earlier. The current progress there is tracked on the website six-speed, which shows the performance of ES2015 and ESNext features compared to their native ES5 counterparts.
The work on optimizing features introduced with ES2015 and beyond is coordinated via a performance plan, where the V8 team gathers and coordinates areas that need improvement, and design documents to tackle those problems.
The current behaviour of the
--harmony flag on Node.js is to enable staged features only. After all, it is now a synonym of
--es_staging. As mentioned above, these are completed features that have not been considered stable yet. If you want to play safe, especially on production environments, consider removing this runtime flag until it ships by default on V8 and, consequently, on Node.js. If you keep this enabled, you should be prepared for further Node.js upgrades to break your code if V8 changes their semantics to more closely follow the standard.
Node.js provides a simple way to list all dependencies and respective versions that ship with a specific binary through the
process global object. In case of the V8 engine, type the following in your terminal to retrieve its version:
node -p process.versions.v8