-
Notifications
You must be signed in to change notification settings - Fork 154
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
it did not throw detail information when error occurs #50
Comments
What version of gulp-uglify and what version of gulp? We've been providing what file failed as part of the error for a while now. |
Same problem here:
gulp 3.8.7 |
Should note that I'm not convinced that a syntax error is causing this error. I'm only using popular libraries and coffeescript output for my source files. I might try narrowing down the problem... Is there any way to get some more debug info from the module? |
gulp-uglify provides detailed information on the error message, via the "fileName", and "lineNumber" properties. Please attach an error handler to the stream. |
Okay, definitely my fault, I was accidentally streaming a css file into uglify. 😊 |
Providing a better documentation on gulp error management is being tracked in gulpjs/gulp#359. |
For others like me, who do not know how to get the error message, here is what you need to do:
|
I had the same problem too, Thank to @devdattaTpoined out how to show an error while compiling gulp uglify. I found out that one of mine .js files has an typo or it spits out an error. Thank you so much check your .js files |
@devdattaT Thanks for share this gulp-util log |
Why not add this info to README.md? |
Thanks, solved my issue as well. |
please update your read me |
@AliMD The README on the 1.2.0 branch contains some documentation on errors. |
hello! I use elixir + gulp, and i get the same error, someone can help me?
|
@mprandot Please see the README for how the use the recommended |
@terinjokes sorry! I found the error, sintax error in one .js in Thanks! |
I'm having the same problem, and I've tried what @devdattaT suggested, but it's still giving me the same information. It stops at the error on events.js. Do I have to pass the error event to gutil.log? |
The fastest solution I've found was to capture the error with this: process.on('uncaughtException', function(error) {
console.log(error);
process.exit(1)
}) I put that snippet in my gulpfile.js and I could figure it out where was the problem. It was a problem in my code. |
If you use
|
when js has syntax error, this plugin output nothing but error stack.
The text was updated successfully, but these errors were encountered: