Skip to content

docs: mention Terser instead of UglifyJS #12808

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

Closed
wants to merge 1 commit into from

Conversation

cexbrayat
Copy link
Member

Now that #11996 landed, the CLI uses Terser instead of UglifyJS.

Now that angular#11996 landed, the CLI uses Terser instead of UglifyJS.
@alan-agius4
Copy link
Collaborator

alan-agius4 commented Oct 30, 2018

Thanks for the PR. However, the documentation here is correct as this is strictly for version 6. Version 7 documentation has been moved to https://angular.io/guide/build

There is currently an open PR to improve the overall descriptions #12741

@cexbrayat cexbrayat deleted the fix/terser branch October 30, 2018 16:45
@cexbrayat
Copy link
Member Author

@alan-agius4 Ha right, sorry.

Maybe this is still interesting for the README of build-optimizer which still mention UglifyJS though?

@alan-agius4
Copy link
Collaborator

If you want to go ahead a remove it that it’s fine by me. Though I suggest not to mention the brand or tool that can be used as strictly speaking it can work with any js optimization tool.

For instance instead of UglifyJS you can use JS optimization tools

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
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 this pull request may close these issues.

3 participants