> As for the general implications of `module` becoming an identifier in es6 on node...that will be interesting.
Wondering how much is Node.js (or server-side JS for that matter) represented in the ES6 process - a couple of Google searches reveal that perhaps not very much: site:mail.mozilla.org/pipermail/es-discuss/ "es6" "node" site:wiki.ecmascript.org nodejs I could be totally wrong, but looking at http://www.ecma-international.org/memento/TC39-M.htm - the 3 most powerful entities in this process seem to be Mozilla, Google, and Microsoft. (Great that at least MS is somehow connected to Node via Azure.) Ironically, it's the server side where new JS standards will be utilized almost immediately, not the browser side. On Feb 15, 11:10 pm, Brandon Benvie <[email protected]> wrote: > Don't use `node --harmony` with this version going forward. A new flag > `--harmony_modules` which causes node to die instantly due to making > "module" an identifier. `node --harmony_typeof --harmony_scoping > --harmony_proxies --harmony_collections` will achieve the desired result. > As for the general implications of `module` becoming an identifier in es6 > on node...that will be interesting. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
