Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ES6] Update mozilla ast #1117

Closed
avdg opened this issue Jun 9, 2016 · 2 comments
Closed

[ES6] Update mozilla ast #1117

avdg opened this issue Jun 9, 2016 · 2 comments

Comments

@avdg
Copy link
Contributor

avdg commented Jun 9, 2016

(Yeah, I'm talking about fixing this mess: avdg@45fcb65)

There is a need to maintain mozilla-ast on the harmony branch if there is a need to keep it alive. As I don't have the tools (yet) to test things out in real-world usage. I don't think about maintaining this right now. However, I did take a quick look and I think one with enough time, interest and resources can do this.

@kzc
Copy link
Contributor

kzc commented Jun 9, 2016

Repeating comment here as it is relevant to this new ticket...

I believe that mozilla-ast import and export for ES5 is complete on master and is compatible with acorn --ecma5, so all new ESTree/mozilla development can take place on the harmony branch for ES6.

  --spidermonkey                Assume input files are SpiderMonkey AST format (
                                as JSON).                              [boolean]

  --dump-spidermonkey-ast       Dump SpiderMonkey AST to stdout.       [boolean]

I don't know if we should make new flags specifically for ES6 import/export?

For that matter, should lib/parser.js support an ES5 parsing mode and a separate ES6 mode as acorn does with --ecma5 and --ecma6?

@alexlamsl
Copy link
Collaborator

Closing as duplicate of #968

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants