Skip to content
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

Cascade error display #1134

Closed
let4be opened this issue Jul 3, 2015 · 3 comments
Closed

Cascade error display #1134

let4be opened this issue Jul 3, 2015 · 3 comments

Comments

@let4be
Copy link

let4be commented Jul 3, 2015

I'm using gulp 4.0
(npm install gulpjs/gulp-cli#4.0 -g)

When one task throws some kind of error the error is being propagated to the root task and I see huge stacktrace for each task, is there any way to get rid of this?

http://hastebin.com/potikeroqa.pl

Expected behavior:
show stack-trace only for the task where error originates from

If I do
throw new gutil.PluginError('test', 'something broke', {showStack: false})
it hides stacktrace completely

Thanks!

@phated
Copy link
Member

phated commented Jul 12, 2015

I'm not sure if we plan to tackle this. If a community member wants to submit some code that attempts to solve it, we will review the possibility of adding the feature.

@phated
Copy link
Member

phated commented Nov 18, 2015

Ref #1330

@phated phated added this to the gulp-cli 1.1.0 milestone Nov 18, 2015
@phated
Copy link
Member

phated commented Dec 18, 2015

Collapsing into #1330 which now has an impl attached

@phated phated closed this as completed Dec 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants