Skip to content

docs: mention Terser instead of UglifyJS - #12808

Closed
cexbrayat wants to merge 1 commit into
angular:masterfrom
cexbrayat:fix/terser
Closed

docs: mention Terser instead of UglifyJS#12808
cexbrayat wants to merge 1 commit into
angular:masterfrom
cexbrayat:fix/terser

Conversation

@cexbrayat

Copy link
Copy Markdown
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

alan-agius4 commented Oct 30, 2018

Copy link
Copy Markdown
Collaborator

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
Copy Markdown
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
Copy Markdown
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
Copy Markdown

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