-
Notifications
You must be signed in to change notification settings - Fork 100
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
Support of ES6 #459
Comments
I actually tried to make the update to uglify3 a few months ago, unsuccessfully. It's not really fresh in my mind anymore, but there were a lot of set backs, and I just had to give up. The API for Surely doable. But not a trivial task to achieve. |
I tried uglify3 last weekend. AST've changed so much. And they do not expose |
I am thinking about really writing a new parser. for javascript part it will aggregate on existing one. |
Hi, I've been watching this project for quite a while(from 2017). It's good to see it is still improving.
I wonder will it support ES6 in the future? It will be very handy.
I've done some investigation.
In qmlweb-parser. It uses gulp to copy uglifyjs 1.3.5's code to support QML. This approach makes it hard to change to new javascript parser(uglify-js3, acorn, esprima) nor can auto complete work properly. And also, it seems the AST tree is a little bit coupling with the QmlEngine and QmlBinding.
The text was updated successfully, but these errors were encountered: