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
The task seems to break whenever a js file has an error. The force flag is unable to proceed it further. #409
Comments
tHBp
changed the title
The task seems the break whenever a js file has an error. The force flag is unable to proceed it further.
The task seems to break whenever a js file has an error. The force flag is unable to proceed it further.
Jun 10, 2016
thefourtheye
added a commit
to thefourtheye/grunt-contrib-uglify
that referenced
this issue
Mar 21, 2018
Fixes: gruntjs#409 Whenever the minification of a file fails, the task fails with the error 'min' is not available in 'undefined'. This patch allows the task to continue to the next file without making any changes to the contents of the file in the destination. Also, this introduces a new configuration option `skipErrors`, so that the users can specify that in the task level options to override the default behaviour.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While using the task on multiple files inside a directory structure, the task fails and stops uglification at the point where it finds the first error. I need the task to log the error and move on to next file. I have tried using --force flag with it and drop_console: true. But still the same.
Is there any option to log the error in the file and then move on to next file for uglification?
The text was updated successfully, but these errors were encountered: