You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docIssues and PRs related to the documentations.errorsIssues and PRs related to JavaScript errors originated in Node.js core.moduleIssues and PRs related to the module subsystem.
(By the way, I'm not finding where the API documents live. Maybe the docs for how to update docs could be surfaced better so this could have taken the form of a PR.)
The text was updated successfully, but these errors were encountered:
(By the way, I'm not finding where the API documents live. Maybe the docs for how to update docs could be surfaced better so this could have taken the form of a PR.)
addaleax
added
doc
Issues and PRs related to the documentations.
module
Issues and PRs related to the module subsystem.
errors
Issues and PRs related to JavaScript errors originated in Node.js core.
labels
Jul 19, 2018
I noticed that MODULE_NOT_FOUND doesn't follow the ERR_* naming conventions like all the other documented codes, but changing the code could be a breaking change for many.
Document `MODULE_NOT_FOUND` as a possible `code` for errors.
Also, some missorting of bottom references was fixed in passing.
PR-URL: #21894Fixes: #21890
Reviewed-By: James M Snell <[email protected]>
docIssues and PRs related to the documentations.errorsIssues and PRs related to JavaScript errors originated in Node.js core.moduleIssues and PRs related to the module subsystem.
The error code
MODULE_NOT_FOUND
doesn't seem to be documented (see https://nodejs.org/dist/latest-v8.x/docs/api/errors.html#nodejs-error-codes). Having it officially supported/documented will help us safely implement "tryRequire" operations for optional files.(By the way, I'm not finding where the API documents live. Maybe the docs for how to update docs could be surfaced better so this could have taken the form of a PR.)
The text was updated successfully, but these errors were encountered: