Closed tunnckoCore closed 6 years ago
hmm, I might not have time to look at this for a few days or longer. if you feel like doing a pr that would be great, otherwise I'll try to take a look later this week or weekend
I don't remember the exact details but it may be caused by the call to the native error constructor. I remember that it has some special behavior that may reset some properties.
I checked this behavior in gulp-util and it's the same. I'm going to close this unless there's a compelling reason (and hopefully a PR)
Name of created error always is
Error
notPluginError
by default. It never sets the name toPluginError
here. So it isError
until we{name: 'MyError'}
.outputs