-
Notifications
You must be signed in to change notification settings - Fork 230
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
support the new error system from core #297
Comments
What I have in mind is creating a new standalone npm module that replicates the functionality of |
how big will that module be? As long as it works down to Node 0.8 (and maybe 0.6) we are good. I'm a bit worried about |
the |
so last time i tried getting custom errors in firefox and other browsers was not really worth it and you end up getting worse stack traces so we may want to investigate what the case is currently becuase if that still the case just having for readable-streams the case where we just add a few properties to the errors and call it a day may end being the best way forward |
As we talked about it in May, core is implementing error codes, and
'stream'
should conform to this rule. The big question is how we port those toreadable-stream
, as I think it might be worthy to keep consistency.I do not want a regexp for each error, so we might have to parse the error definition file and/or do some form or processing of that one as well.
cc @jasnell
Example: nodejs/node@d50a802
The text was updated successfully, but these errors were encountered: