Skip to content

Conversation

mhamel06
Copy link
Contributor

@mhamel06 mhamel06 commented Aug 9, 2016

Fix #1836

@clydin
Copy link
Member

clydin commented Aug 9, 2016

Could the warnings be hidden behind a verbose command line option? They could be useful to some.

@filipesilva
Copy link
Contributor

@TheLarkInn, what do you think?

@alexciesielski
Copy link

+1, warnings in production should be opt-in

@Brocco
Copy link
Contributor

Brocco commented Oct 14, 2016

This needs to be configurable based upon a flag on the build command.

@alexciesielski
Copy link

Actually I would rather have these warnings in development mode with actual line numbers so I can fix those warnings then.

@clydin
Copy link
Member

clydin commented Oct 14, 2016

They are not actually warnings. They are a list of uglifyjs optimization actions.

@hansl
Copy link
Contributor

hansl commented Dec 3, 2016

This was made obsolete by the latest changes to logging.

@hansl hansl closed this Dec 3, 2016
@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 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Many Warnings from UglifyJs on --prod build: WebPack
7 participants