On May 21, 2015, at 10:48 AM, Nick Santos wrote:
> Are the errors thrown by the 'fs' module documented or expected to be stable?
>
> As an example, if I run
> fs.statSync('file-that-does-not-exist.js')
> it throws an error with error.code == 'ENOENT'
>
> Is it OK to rely on this code as a stable part of the API? Are the possible
> error codes enumerated anywhere?
This package may help:
https://www.npmjs.com/package/errno-codes
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/B01D3830-F86D-43BE-A61C-E9B8E8D30DA4%40ryandesign.com.
For more options, visit https://groups.google.com/d/optout.
