Repository navigation
ES6: Clarify difference between --es_staging vs --harmony flags #694
Description
Quoting @williamkapke #674 (comment)
I guess there could be more clarification on the difference of the
--es_stagingvs--harmonyflags. From the existing page, I concluded they were the aliases of each other. I guess that isn't true:
See: compat-table/node-compat-table#1 (comment)
I've never used those flags myself, can someone explain the difference?
/cc @nodejs/collaborators
Activity
bnoordhuis commentedon Apr 27, 2016
In v4 and v5, they're synonyms for beta-level features: considered complete but not battle-tested yet; can still have bugs.
In v6,
--es_stagingis--harmonyplus a few alpha-level features; currently--harmony_regexp_lookbehindand--harmony_tailcallsbut that can change at any time.ChALkeR commentedon May 3, 2016
Note that
--es-stagingis labeled as «for internal use only» and exposes more unstable features, while the change that got landed promotes--es-stagingover--harmony.fhemberger commentedon May 3, 2016
@ChALkeR Good catch, the "for internal use" remark was not present in Node.js 4.3.1. So we should rather document the
--harmonyflag only and leave out--es_staging?ChALkeR commentedon May 3, 2016
@fhemberger In Node.js 4.3.1 those two were equivalent.
/cc @nodejs/documentation
fhemberger commentedon May 3, 2016
@ChALkeR Yes, but in Node.js 6.0 they are not and
--es_stagingis flagged "for internal use". But in all versions--harmonydoes the same, so we should use this flag in our documentation and omit the internal flag--es_staging.ChALkeR commentedon May 3, 2016
… except for 0.10/0.12.
lpinca commentedon May 3, 2016
I agree.
ES6: Remove description of `--es_staging` flag
fhemberger commentedon May 3, 2016
Fixed on 139393e.