You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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 tokenizer and parse have been updated. It didn't seem like much at first... but I still wasn't able to get it to work.
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: