-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
Error logging #817
Comments
There is now doc page about errors that explains these codes |
Could this information be displayed directly in the console (at least in a debug/development mode) ? |
Thank you for the link. It's very helpful. |
To log the error, you can use the errno module : npm install errno
node -e "var fs = require('fs'); var codes = require('errno').code; try{ fs.readFileSync('/nosuchfile') } catch(e){ console.log(codes[e.code]) }" |
It's good but it still requires an additional action. I think it's not very developer friendly. |
Kinda a dupe of #92. I think the new error docs should be fine for now? |
Thank you @Fishrock123 for the pointer. I would say it looks more like a dup of #212. |
Oh yes. That too. Closing in favor of #212 @frankrousseau, please share your thoughts there. :) |
Reopening as #212 got closed and this can still improve, imo. |
I think this is working as intended. These are standard POSIX error codes, consult |
We got new error docs a while ago. :) |
Hello there,
On Node.js most error loggings are awful (ex:
ENOENT
error). Most of the time it requires a web research to find its meaning.Is it possible to improve this in io.js ? I mean, if I don't find any technical constraints, may I propose a pull request about it?
The text was updated successfully, but these errors were encountered: