Skip to content
This repository was archived by the owner on Aug 7, 2021. It is now read-only.

Upgrade to use Uglify-es branch #212

Closed
NathanaelA opened this issue Jul 4, 2017 · 2 comments · Fixed by #401
Closed

Upgrade to use Uglify-es branch #212

NathanaelA opened this issue Jul 4, 2017 · 2 comments · Fixed by #401

Comments

@NathanaelA
Copy link

Please upgrade the nativescript-webpack code to use the ES code branch:

https://github.com/noBlubb/uglify-es-webpack-plugin

The issue is that if you used any ES6 code; and then attempt to use the --uglify flag; it will fail because uglify (non-es) doesn't support es6 constructs.

Some of my plugins are written as pure ES6, and so they cannot be webpacked with --uglify because of this issue... In addition if TypeScript is set to emit ES6 code; this issue will also occur.

@sis0k0 sis0k0 added this to the 1.0 milestone Jul 5, 2017
@terreb
Copy link

terreb commented Sep 1, 2017

Any progress with this guys? I came across an issue when trying to use typescript powered Nativescript app + some plugins. Is there a recommended workaround to uglify es6 code until official support for es6+uglify is added?

@gabitoesmiapodo
Copy link

Any news on this?

If someone could share a workaround in the meantime, it would be nice.

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

Successfully merging a pull request may close this issue.

4 participants