<p>On joyent/
[email protected] (V8 3.26), the
<code>--harmony
</code> runtime flag enabled all
<strong>completed
</strong>,
<strong>staged
</strong> and
<strong>in progress
</strong> ES6 features together, in bulk (with the exception of nonstandard/non-harmonious semantics for
<code>typeof
</code> which were hidden under
<code>--harmony-typeof
</code>). This meant that some really buggy or even broken features like
<a href="
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy"
>proxies
</a> were just as readily available for developers as
<a href="
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/function*"
>generators
</a>, which had very little or even no known-issues. As such, it was best practice to either enable only certain features by using specific runtime harmony feature flags (e.g.
<code>--harmony-generators
</code>), or simply enable all of them and then use a restricted subset.
</p>
0 commit comments