-
Notifications
You must be signed in to change notification settings - Fork 11
Investigate the possibility to port to UglifyJS 2 #4
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
Comments
This is technically possible and not so hard to do, but the new output from UglifyJS2 is much more vebrose — this means that the runtime will consume more memory and will require to load larger files from the server when in pre-parsed mode. We could investigate converting that into a shorter form suitable to use by qmlweb, though, but that will still slow down parsing. Also, the parser itself became about two times larger (and I included only the required files). |
Filed a patch to Update: merged. |
uglify-js-2 branch has some initial work, mostly broken. It also requires the abovementioned UglifyJS2 patch. |
Probably after #3.
The text was updated successfully, but these errors were encountered: