Alex Liu

Thanks @jmm, appreciate the info and the links. I had a lot of trouble trying to "recreate" the records. I'd get inconsistent output from the stream when doing so, probably...

Once 5.x lands this will become the default behavior, as all errors created by restify-errors inherit from VError.

Oops - really sorry for not following up on this thread. I may have been confused, and thought you were asking about restify 4.x. Are you basically wanting to create...

Hi @kobymolcho, do you have a sample code snippet here to reproduce the exact exception you are seeing? Anything involving the `%` does sound sprintf related but want to make...

Thanks! What version of restify-errors are you using? If you reduce it down to just these two lines, can you confirm the exception you are seeing: ```js const errs =...

Thanks for the confirmation. This is expected behavior - you can work around it for now: ```js var err = new errs.NotFoundError('%s', '1234%25d1234'); ``` Alternatively, some work is happening over...

As it looks like this was resolved (and behavior was expected), I'll close this ticket now. @kobymolcho let us know if that isn't the case.

Hi all - what version of restify-errors are you using? This should work on latest 7.0.0 release: ```js const errs = require('restify-errors'); const MyErr = errs.makeConstructor('MyError'); throw new MyErr('boom'); ```...

VError has made progress over in davepacheco/node-verror#10. Look to see how we can merge that functionality back in.

I agree it's a special case, though doing a proper exports will allow people to use Browserify as well without any extra config necessary. I'll try to whip up something...