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

Design question - why was acorn-jsx chosen instead the standard acorn parser #40

Open
shanemcandrewai opened this issue Oct 12, 2021 · 0 comments

Comments

@shanemcandrewai
Copy link

shanemcandrewai commented Oct 12, 2021

Hello,

I tried transpiling the Ace editor tree to ES6 but it failed due to several problems such as missing file extensions (.js) on the import module-names and Error: Dynamic module names are not supported, so I had to dig into the code which leads to my question - why was acorn-jsx chosen instead the standard acorn parser?

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

No branches or pull requests

1 participant