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

feat: use terser to replace uglifyjs for better es6 support #907

Merged
merged 1 commit into from
Jul 27, 2018
Merged

feat: use terser to replace uglifyjs for better es6 support #907

merged 1 commit into from
Jul 27, 2018

Conversation

3cp
Copy link
Member

@3cp 3cp commented Jul 27, 2018

Terser is the current active fork of uglify-es. This is not only required to support babel targeting es6, but also improve compatibility of any vendor js code which uses "const".

closes #883, #490, supersedes #864

Terser is the current active fork of uglify-es. This is not only required to support babel targeting es6, but also improve compatibility of any vendor js code which uses "const".

closes #883, #490, supersedes #864
@JeroenVinke JeroenVinke merged commit bad8f8a into aurelia:master Jul 27, 2018
@3cp 3cp deleted the use-terser-to-replace-uglifyjs branch August 10, 2018 01:24
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

Successfully merging this pull request may close these issues.

Production builds fail on Uglify step when TypeScript target is ES6
2 participants